svn commit: r860599 - in /websites/production/activemq/content: cache/main.pageCache failover-transport-reference.html jmx.html

[bu...@apache.org]

Author: buildbot
Date: Thu May  2 13:21:36 2013
New Revision: 860599

Log:
Production update by buildbot for activemq

Modified:
    websites/production/activemq/content/cache/main.pageCache
    websites/production/activemq/content/failover-transport-reference.html
    websites/production/activemq/content/jmx.html

Modified: websites/production/activemq/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/activemq/content/failover-transport-reference.html
==============================================================================
--- websites/production/activemq/content/failover-transport-reference.html (original)
+++ websites/production/activemq/content/failover-transport-reference.html Thu May  2 13:21:36 2013
@@ -143,7 +143,7 @@ Starting in version 5.3.1, redelivery or
 <p>There are some options that are available on a TransportConnector that is used by the broker that can be used to update clients automatically with information about new brokers to failover to. These are:</p>
 
 <div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"> Option Name </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"> updateClusterClients </td><td colspan="1" rowspan="1" class="confluenceTd"> false </td><td colspan="1" rowspan="1" class="confluenceTd"> if true, pass information to connected clients about changes in the topology of the broker cluster </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> rebalanceClusterClients </td><td colspan="1" rowspan="1" class="confluenceTd"> false </td><td colspan="1" rowspan="1" class="confluenceTd"> if true, connected clients will be asked to rebalance across a cluster of brokers when a new broker joins the network of brokers </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> updateClusterClientsOnRemove </td><td colspan="1" ro
 wspan="1" class="confluenceTd"> false </td><td colspan="1" rowspan="1" class="confluenceTd"> if true, 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 not when brokers leave. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> updateClusterFilter </td><td colspan="1" rowspan="1" class="confluenceTd"> null </td><td colspan="1" rowspan="1" class="confluenceTd"> 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 </td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"> Option Name </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"> updateClusterClients </td><td colspan="1" rowspan="1" class="confluenceTd"> false </td><td colspan="1" rowspan="1" class="confluenceTd"> if true, pass information to connected clients about changes in the topology of the broker cluster </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> rebalanceClusterClients </td><td colspan="1" rowspan="1" class="confluenceTd"> false </td><td colspan="1" rowspan="1" class="confluenceTd"> if true, connected clients will be asked to rebalance across a cluster of brokers when a new broker joins the network of brokers (note: priorityBackup=true can override) </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> updateClust
 erClientsOnRemove </td><td colspan="1" rowspan="1" class="confluenceTd"> false </td><td colspan="1" rowspan="1" class="confluenceTd"> if true, 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 not when brokers leave. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> updateClusterFilter </td><td colspan="1" rowspan="1" class="confluenceTd"> null </td><td colspan="1" rowspan="1" class="confluenceTd"> 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 </td></tr></tbody></table>
 </div>
 
 

Modified: websites/production/activemq/content/jmx.html
==============================================================================
--- websites/production/activemq/content/jmx.html (original)
+++ websites/production/activemq/content/jmx.html Thu May  2 13:21:36 2013
@@ -80,8 +80,7 @@
 
 <p>You can enable/disable JMX support as follows...</p>
 
-<p>1. Run a broker setting the broker property useJmx to true (enabled by default)<br clear="none">
-i.e.</p>
+<p>1. <a shape="rect" href="run-broker.html" title="Run Broker">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" style="border-width: 1px;"><div class="codeContent panelContent">
@@ -91,12 +90,6 @@ i.e.</p>
 &lt;/broker&gt;
 </pre>
 </div></div>
-<p>For url configuration</p>
-<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
-<pre class="code-java">
-broker:(tcp:<span class="code-comment">//localhost:61616)?useJmx=<span class="code-keyword">true</span></span>
-</pre>
-</div></div>
 
 <p>2. Run a JMX console </p>