qpid-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kw...@apache.org
Subject svn commit: r1576538 [1/13] - in /qpid/site: docs/ docs/components/qpid-jms/ docs/releases/qpid-0.26/ docs/releases/qpid-0.26/java-broker/ docs/releases/qpid-0.26/java-broker/book/ docs/releases/qpid-0.26/jms-client-0-8/ docs/releases/qpid-0.26/jms-cli...
Date Tue, 11 Mar 2014 22:52:45 GMT
Author: kwall
Date: Tue Mar 11 22:52:42 2014
New Revision: 1576538

URL: http://svn.apache.org/r1576538
Log:
QPID-5618: Improve site links to JMS client documentation

* Republish java broker and jms-client docbooks for trunk/0.26
* Republish static site files with links to the JMS documentation.


Added:
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/book/
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/book/JMS-Client-0-8-Appendix-Exceptions.html
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/book/JMS-Client-0-8-Appendix-Maven.html
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/book/JMS-Client-0-8-Binding-URL.html
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding-Connection.html
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding-ConnectionFactory.html
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding-Destinations.html
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding-MessageConsumer.html
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding-MessageProducer.html
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding-Session.html
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding.html
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/book/JMS-Client-0-8-Connection-URL.html
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/book/JMS-Client-0-8-Document-Scope-And-Intended-Audience.html
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/book/JMS-Client-0-8-Examples-PubSub.html
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/book/JMS-Client-0-8-Examples.html
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/book/JMS-Client-0-8-Introduction.html
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/book/JMS-Client-0-8-JMS-Getting-And-Dependencies-Dependencies.html
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/book/JMS-Client-0-8-JMS-Getting-And-Dependencies.html
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/book/JMS-Client-0-8-JNDI-Properties-Format-Destination.html
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/book/JMS-Client-0-8-JNDI-Properties-Format-Queue.html
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/book/JMS-Client-0-8-JNDI-Properties-Format-Topic.html
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/book/JMS-Client-0-8-JNDI-Properties-Format.html
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/book/JMS-Client-0-8-Logging-EnablingDebugLogging.html
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/book/JMS-Client-0-8-Logging.html
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/book/JMS-Client-0-8-System-Properties.html
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/book/css/
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/book/css/style.css
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/book/images/
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/book/images/JndiOverview.png   (with props)
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/book/images/QpidJmsOverview.png   (with props)
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/book/index.html
    qpid/site/docs/releases/qpid-0.26/jms-client-0-8/jms_client08-book.pdf   (with props)
Modified:
    qpid/site/docs/components/qpid-jms/index.html
    qpid/site/docs/documentation.html
    qpid/site/docs/releases/qpid-0.26/index.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Close-Connection-When-No-Route.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Concepts-Exchanges.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Concepts-Virtual-Hosts.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Concepts.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Configuring-And-Managing-HTTP-Management.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Configuring-And-Managing.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-Backup.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-ClientFailover.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-Configuration.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-DisasterRecovery.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-DurabilityGuarantee.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-JMXAPI.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-MigrationFromNonHA.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-Monitoring-cluster.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-OfferingsOfJavaBroker.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-Performance.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-TwoNodeCluster.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Introduction.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Queues.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Runtime-Disk-Space-Management.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Security.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Stores-BDB-Store-Configuration.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Stores-Derby-Store-Configuration.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Stores-JDBC-Store-Configuration.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Stores-Memory-Store-Configuration.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Virtual-Host-Binding-Queue.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Virtual-Host-Configuration-Exchange.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Virtual-Host-Configuration-File-Example.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Virtual-Host-Configure-Disk-Quotas.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Virtual-Host-Configure-Flow-Control.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Virtual-Host-Configuring-DLQ.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Virtual-Host-Declare-Queues.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Virtual-Host-Transaction-Timeout-Configuring.html
    qpid/site/docs/releases/qpid-0.26/java-broker/book/index.html
    qpid/site/docs/releases/qpid-0.26/java-broker/java-broker-book.pdf
    qpid/site/docs/releases/qpid-0.26/release-notes.html
    qpid/site/docs/releases/qpid-trunk/cpp-broker/book/AMQP-Compatibility.html
    qpid/site/docs/releases/qpid-trunk/cpp-broker/book/QpidInteroperabilityDocumentation-QpidInteroperabilityDocumentation.html
    qpid/site/docs/releases/qpid-trunk/cpp-broker/book/Using-message-groups.html
    qpid/site/docs/releases/qpid-trunk/cpp-broker/book/ch01.html
    qpid/site/docs/releases/qpid-trunk/cpp-broker/book/ch01s02.html
    qpid/site/docs/releases/qpid-trunk/cpp-broker/book/ch01s03.html
    qpid/site/docs/releases/qpid-trunk/cpp-broker/book/ch01s06.html
    qpid/site/docs/releases/qpid-trunk/cpp-broker/book/ch02s02.html
    qpid/site/docs/releases/qpid-trunk/cpp-broker/book/ch02s03.html
    qpid/site/docs/releases/qpid-trunk/cpp-broker/book/chapter-Managing-CPP-Broker.html
    qpid/site/docs/releases/qpid-trunk/cpp-broker/book/chapter-ha.html
    qpid/site/docs/releases/qpid-trunk/cpp-broker/book/ha-queue-replication.html
    qpid/site/docs/releases/qpid-trunk/cpp-broker/book/index.html
    qpid/site/docs/releases/qpid-trunk/cpp-broker/book/pr01.html
    qpid/site/docs/releases/qpid-trunk/cpp-broker/book/producer-flow-control.html
    qpid/site/docs/releases/qpid-trunk/cpp-broker/cpp-broker-book.pdf
    qpid/site/docs/releases/qpid-trunk/index.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-Appendix-Environment-Variables.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-Appendix-System-Properties.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-Close-Connection-When-No-Route.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-Concepts-Exchanges.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-Concepts-Virtual-Hosts.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-Concepts.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-Configuring-And-Managing-HTTP-Management.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-Configuring-And-Managing-JMX-Management.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-Configuring-And-Managing.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-High-Availability-Backup.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-High-Availability-ClientFailover.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-High-Availability-Configuration.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-High-Availability-DisasterRecovery.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-High-Availability-DurabilityGuarantee.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-High-Availability-JMXAPI.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-High-Availability-MigrationFromNonHA.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-High-Availability-Monitoring-cluster.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-High-Availability-OfferingsOfJavaBroker.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-High-Availability-Performance.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-High-Availability-TwoNodeCluster.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-High-Availability.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-Introduction.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-Queues.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-Runtime-Disk-Space-Management.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-Security.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-Stores-BDB-Store-Configuration.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-Stores-Derby-Store-Configuration.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-Stores-JDBC-Store-Configuration.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-Stores-Memory-Store-Configuration.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-Virtual-Host-Binding-Queue.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-Virtual-Host-Configuration-Exchange.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-Virtual-Host-Configuration-File-Example.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-Virtual-Host-Configure-Disk-Quotas.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-Virtual-Host-Configure-Flow-Control.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-Virtual-Host-Configuring-DLQ.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-Virtual-Host-Declare-Queues.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/Java-Broker-Virtual-Host-Transaction-Timeout-Configuring.html
    qpid/site/docs/releases/qpid-trunk/java-broker/book/index.html
    qpid/site/docs/releases/qpid-trunk/java-broker/java-broker-book.pdf
    qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Appendix-Exceptions.html
    qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Appendix-Maven.html
    qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Binding-URL.html
    qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding-Connection.html
    qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding-ConnectionFactory.html
    qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding-Session.html
    qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Client-Understanding.html
    qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Connection-URL.html
    qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Examples-PubSub.html
    qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-Examples.html
    qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/JMS-Client-0-8-System-Properties.html
    qpid/site/docs/releases/qpid-trunk/jms-client-0-8/book/index.html
    qpid/site/docs/releases/qpid-trunk/jms-client-0-8/jms_client08-book.pdf
    qpid/site/input/releases/qpid-0.26/index.md
    qpid/site/input/releases/qpid-0.26/release-notes.md

Modified: qpid/site/docs/components/qpid-jms/index.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/components/qpid-jms/index.html?rev=1576538&r1=1576537&r2=1576538&view=diff
==============================================================================
--- qpid/site/docs/components/qpid-jms/index.html (original)
+++ qpid/site/docs/components/qpid-jms/index.html Tue Mar 11 22:52:42 2014
@@ -147,21 +147,51 @@ older protocol versions.</p>
 
 <h2 id="documentation">Documentation</h2>
 
-<p>This is the documentation for the current released version.  You can
+<p>This is the documentation for the current released versions.  You can
 find previous versions with our
 <a href="/releases/index.html#past-releases">past releases</a>.</p>
 
 <div class="two-column">
 
 <ul>
-<li><a href="/releases/qpid-0.26/programming/book/QpidJMS.html">Using the Qpid JMS client</a></li>
 <li><a href="http://docs.oracle.com/javaee/1.4/api/javax/jms/package-summary.html">API reference</a></li>
-<li><a href="/releases/qpid-0.26/qpid-jms/examples/index.html">Examples</a></li>
 <li><a href="https://cwiki.apache.org/confluence/display/qpid/qpid+java+build+how+to">How to build Qpid Java</a></li>
 </ul>
 
 </div>
 
+<h3 id="qpid-amqp-10-client">Qpid AMQP 1.0 client</h3>
+
+<div class="two-column">
+
+<ul>
+<li><a href="http://svn.apache.org/repos/asf/qpid/branches/0.26/qpid/java/amqp-1-0-client-jms/example">Examples</a></li>
+</ul>
+
+</div>
+
+<h3 id="qpid-java-client-with-amqp-0-10">Qpid Java client with AMQP 0-10</h3>
+
+<div class="two-column">
+
+<ul>
+<li><a href="/releases/qpid-0.26/programming/book/QpidJMS.html">Using the Qpid JMS client</a></li>
+<li><a href="/releases/qpid-0.26/qpid-jms/examples/index.html">Examples</a></li>
+</ul>
+
+</div>
+
+<h3 id="qpid-java-client-with-amqp-0-910-8">Qpid Java client with AMQP 0-91..0-8</h3>
+
+<div class="two-column">
+
+<ul>
+<li><a href="/releases/qpid-0.26/jms-client-0-8/book/index.html">Using the Qpid JMS client</a></li>
+<li><a href="/releases/qpid-0.26/jms-client-0-8/book/JMS-Client-0-8-Examples.html">Examples</a></li>
+</ul>
+
+</div>
+
 <h2 id="issues">Issues</h2>
 
 <p>For more information about finding and reporting bugs, see

Modified: qpid/site/docs/documentation.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/documentation.html?rev=1576538&r1=1576537&r2=1576538&view=diff
==============================================================================
--- qpid/site/docs/documentation.html (original)
+++ qpid/site/docs/documentation.html Tue Mar 11 22:52:42 2014
@@ -169,9 +169,9 @@ find older versions with our
 
 <ul>
 <li><a href="/components/qpid-jms/index.html">Overview</a></li>
-<li><a href="/releases/qpid-0.26/programming/book/QpidJMS.html">Using the Qpid JMS client</a> (<a href="/releases/qpid-0.26/programming/programming-book.pdf">PDF</a>)</li>
+<li><a href="/components/qpid-jms/index.html#Documentation">Using the Qpid JMS client</a></li>
 <li><a href="http://docs.oracle.com/javaee/1.4/api/javax/jms/package-summary.html">API reference</a></li>
-<li><a href="/releases/qpid-0.26/qpid-jms/examples/index.html">Examples</a></li>
+<li><a href="/components/qpid-jms/index.html#Documentation">Examples</a></li>
 </ul>
 
 </section>
@@ -276,7 +276,7 @@ find older versions with our
 <ul>
 <li><a href="/releases/index.html">Qpid releases</a></li>
 <li><a href="/components/index.html">Qpid components</a></li>
-<li><a href="/resources.html#trunk-documentation">Trunk documentation</a></li>
+<li><a href="/releases/qpid-trunk/index.html">Trunk documentation</a></li>
 </ul>
 
 

Modified: qpid/site/docs/releases/qpid-0.26/index.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-0.26/index.html?rev=1576538&r1=1576537&r2=1576538&view=diff
==============================================================================
--- qpid/site/docs/releases/qpid-0.26/index.html (original)
+++ qpid/site/docs/releases/qpid-0.26/index.html Tue Mar 11 22:52:42 2014
@@ -208,9 +208,9 @@ available in the full source artefact.</
 <h3 id="qpid-jms">Qpid JMS</h3>
 
 <ul>
-<li><a href="programming/book/QpidJMS.html">Using the Qpid JMS client</a> (<a href="programming/programming-book.pdf">PDF</a>)</li>
 <li><a href="http://docs.oracle.com/javaee/1.4/api/javax/jms/package-summary.html">API reference</a></li>
-<li><a href="qpid-jms/examples/index.html">Examples</a></li>
+<li>Using the Qpid JMS client with <a href="programming/book/QpidJMS.html">AMQP 0-10</a> (<a href="programming/programming-book.pdf">PDF</a>), or <a href="jms-client-0-8/book/index.html">AMQP 0-91..0-8</a> (<a href="jms-client-0-8/jms_client08-book.pdf">PDF</a>)</li>
+<li>Examples for <a href="http://svn.apache.org/repos/asf/qpid/branches/0.26/qpid/java/amqp-1-0-client-jms/example">AMQP 1.0</a>, <a href="qpid-jms/examples/index.html">AMQP 0-10</a>, or  <a href="jms-client-0-8/book/JMS-Client-0-8-Examples.html">0-91..0-8</a></li>
 </ul>
 
 <h3 id="qpid-messaging-api">Qpid Messaging API</h3>

Modified: qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Close-Connection-When-No-Route.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Close-Connection-When-No-Route.html?rev=1576538&r1=1576537&r2=1576538&view=diff
==============================================================================
--- qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Close-Connection-When-No-Route.html (original)
+++ qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Close-Connection-When-No-Route.html Tue Mar 11 22:52:42 2014
@@ -132,7 +132,7 @@
     </p><p>
         Setting the <span class="emphasis"><em>closeWhenNoRoute</em></span> in the JMS client connection URL can override the broker configuration
         on a connection specific basis, for example :
-    </p><div class="example"><a id="idm140218886789520"></a><p class="title"><strong>Example&#160;12.1.&#160;Disable feature to close connection on unroutable messages with client URL</strong></p><div class="example-contents"><pre class="screen">
+    </p><div class="example"><a id="idp1196224"></a><p class="title"><strong>Example&#160;12.1.&#160;Disable feature to close connection on unroutable messages with client URL</strong></p><div class="example-contents"><pre class="screen">
 amqp://guest:guest@clientid/?brokerlist='tcp://localhost:5672'&amp;closeWhenNoRoute='false'</pre></div></div><br class="example-break" /><p>
        If no value is specified on the client the broker setting will be used. If client setting is specified then it will take precedence
        over the broker-wide configuration. If the client specifies and broker does not support this feature the warning will be logged.

Modified: qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Concepts-Exchanges.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Concepts-Exchanges.html?rev=1576538&r1=1576537&r2=1576538&view=diff
==============================================================================
--- qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Concepts-Exchanges.html (original)
+++ qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Concepts-Exchanges.html Tue Mar 11 22:52:42 2014
@@ -125,7 +125,7 @@
     binding argument specifying a JMS message selector</a>.
    </p><p>This exchange type is often used to implement point to point messaging. When used in this manner, the normal
    convention is that the binding key matches the name of the queue. It is also possible to use this exchange type
-   for multi-cast, in this case the same binding key is associated with many queues.</p><div class="figure"><a id="idm140218887586960"></a><p class="title"><strong>Figure&#160;4.3.&#160;Direct exchange</strong></p><div class="figure-contents"><div class="mediaobject"><img alt="Direct exchange" src="images/Exchange-Direct.png" /></div></div></div><br class="figure-break" /><p>The figure above illustrates the operation of direct exchange type. The yellow messages published with the routing key
+   for multi-cast, in this case the same binding key is associated with many queues.</p><div class="figure"><a id="idp391360"></a><p class="title"><strong>Figure&#160;4.3.&#160;Direct exchange</strong></p><div class="figure-contents"><div class="mediaobject"><img alt="Direct exchange" src="images/Exchange-Direct.png" /></div></div></div><br class="figure-break" /><p>The figure above illustrates the operation of direct exchange type. The yellow messages published with the routing key
     "<code class="literal">myqueue</code>" match the binding key corresponding to queue "<code class="literal">myqueue</code>" and so are routed there.  The red
     messages published with the routing key "<code class="literal">foo</code>" match two bindings in the table so a copy of the message is
     routed to both the "<code class="literal">bar1</code>" and "<code class="literal">bar2</code>" queues.</p><p>The routing key of the blue message matches no binding keys, so the message is unroutable. It is handled as described
@@ -133,25 +133,25 @@
      binding key pattern defined by the queue binding. Routing keys are formed from one or more words, with each word delimited
      by a full-stop (.). The pattern matching characters are the * and # symbols. The * symbol matches a single word  and the #
      symbol matches zero or more words.</p><p>Additional filter rules may be specified using a <a class="link" href="Java-Broker-Concepts-Exchanges.html#Java-Broker-Concepts-Exchanges-BindingArguments-JMSSelector" title="4.3.3.1.&#160;JMS Selector">
-     binding argument specifying a JMS message selector</a>.</p><p>The following three figures help explain how the topic exchange functions.</p><p /><div class="figure"><a id="idm140218887575664"></a><p class="title"><strong>Figure&#160;4.4.&#160;Topic exchange - exact match on topic name</strong></p><div class="figure-contents"><div class="mediaobject"><img alt="Topic exchange - exact match on topic name" src="images/Exchange-Topic.png" /></div></div></div><br class="figure-break" /><p>The figure above illustrates publishing messages with routing key "<code class="literal">weather</code>". The exchange routes each
-    message to every bound queue whose binding key matches the routing key.</p><p>In the case illustrated, this means that each subscriber's queue receives every yellow message.</p><div class="figure"><a id="idm140218887571168"></a><p class="title"><strong>Figure&#160;4.5.&#160;Topic exchange - matching on hierarchical topic patterns</strong></p><div class="figure-contents"><div class="mediaobject"><img alt="Topic exchange - matching on hierarchical topic patterns" src="images/Exchange-Topic-Hierarchical.png" /></div></div></div><br class="figure-break" /><p>The figure above illustrates publishing messages with hierarchical routing keys. As before, the exchange routes each
+     binding argument specifying a JMS message selector</a>.</p><p>The following three figures help explain how the topic exchange functions.</p><p /><div class="figure"><a id="idp402944"></a><p class="title"><strong>Figure&#160;4.4.&#160;Topic exchange - exact match on topic name</strong></p><div class="figure-contents"><div class="mediaobject"><img alt="Topic exchange - exact match on topic name" src="images/Exchange-Topic.png" /></div></div></div><br class="figure-break" /><p>The figure above illustrates publishing messages with routing key "<code class="literal">weather</code>". The exchange routes each
+    message to every bound queue whose binding key matches the routing key.</p><p>In the case illustrated, this means that each subscriber's queue receives every yellow message.</p><div class="figure"><a id="idp407440"></a><p class="title"><strong>Figure&#160;4.5.&#160;Topic exchange - matching on hierarchical topic patterns</strong></p><div class="figure-contents"><div class="mediaobject"><img alt="Topic exchange - matching on hierarchical topic patterns" src="images/Exchange-Topic-Hierarchical.png" /></div></div></div><br class="figure-break" /><p>The figure above illustrates publishing messages with hierarchical routing keys. As before, the exchange routes each
     message to every bound queue whose binding key matches the routing key but as the binding keys contain wildcards, the
     wildcard rules described above apply.</p><p>In the case illustrated, <code class="literal">sub1</code> has received the red and green message as "<code class="literal">news.uk</code>" and "<code class="literal">news.de</code>"
     match binding key "<code class="literal">news.#</code>". The red message has also gone to <code class="literal">sub2</code> and <code class="literal">sub3</code> as it's routing key
     is matched exactly by "<code class="literal">news.uk</code>" and by "<code class="literal">*.uk</code>".</p><p>The routing key of the yellow message matches no binding keys, so the message is unroutable. It is handled as described
-    in <a class="xref" href="Java-Broker-Concepts-Exchanges.html#Java-Broker-Concepts-Exchanges-UnroutableMessage" title="4.3.4.&#160;Unrouteable Messages">Section&#160;4.3.4, &#8220;Unrouteable Messages&#8221;</a>.</p><div class="figure"><a id="idm140218887562192"></a><p class="title"><strong>Figure&#160;4.6.&#160;Topic exchange - matching on JMS message selector</strong></p><div class="figure-contents"><div class="mediaobject"><img alt="Topic exchange - matching on JMS message selector" src="images/Exchange-Topic-JMSSelector.png" /></div></div></div><br class="figure-break" /><p>The figure above illustrates messages with properties published with routing key "<code class="literal">shipping</code>".</p><p>As before, the exchange routes each message to every bound queue whose binding key matches the routing key but as a JMS selector
+    in <a class="xref" href="Java-Broker-Concepts-Exchanges.html#Java-Broker-Concepts-Exchanges-UnroutableMessage" title="4.3.4.&#160;Unrouteable Messages">Section&#160;4.3.4, &#8220;Unrouteable Messages&#8221;</a>.</p><div class="figure"><a id="idp416416"></a><p class="title"><strong>Figure&#160;4.6.&#160;Topic exchange - matching on JMS message selector</strong></p><div class="figure-contents"><div class="mediaobject"><img alt="Topic exchange - matching on JMS message selector" src="images/Exchange-Topic-JMSSelector.png" /></div></div></div><br class="figure-break" /><p>The figure above illustrates messages with properties published with routing key "<code class="literal">shipping</code>".</p><p>As before, the exchange routes each message to every bound queue whose binding key matches the routing key but as a JMS selector
     argument has been specified, the expression is evaluated against each matching message. Only messages whose message header values or properties
     match the expression are routed to the queue.</p><p>In the case illustrated, <code class="literal">sub1</code> has received the yellow and blue message as their property "<code class="literal">area</code>"
     cause expression "<code class="literal">area in ('Forties', 'Cromarty')</code>" to evaluate true.  Similarly, the yellow message has also gone to
     <code class="literal">gale_alert</code> as its property "<code class="literal">speed</code>" causes expression "<code class="literal">speed &gt; 7 and speed &lt; 10</code>"
     to evaluate true.</p><p>The properties of purple message cause no expressions to evaluate true, so the message is unroutable. It is handled as described in
     <a class="xref" href="Java-Broker-Concepts-Exchanges.html#Java-Broker-Concepts-Exchanges-UnroutableMessage" title="4.3.4.&#160;Unrouteable Messages">Section&#160;4.3.4, &#8220;Unrouteable Messages&#8221;</a>.</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="Java-Broker-Concepts-Exchanges-Types-Fanout"></a>4.3.2.3.&#160;Fanout</h4></div></div></div><p>The fanout exchange type routes messages to all queues bound to the exchange, regardless of the message's routing key.</p><p>Filter rules may be specified using a <a class="link" href="Java-Broker-Concepts-Exchanges.html#Java-Broker-Concepts-Exchanges-BindingArguments-JMSSelector" title="4.3.3.1.&#160;JMS Selector">
-    binding argument specifying a JMS message selector</a>.</p><div class="figure"><a id="idm140218887550048"></a><p class="title"><strong>Figure&#160;4.7.&#160;Fanout exchange</strong></p><div class="figure-contents"><div class="mediaobject"><img alt="Fanout exchange" src="images/Exchange-Fanout.png" /></div></div></div><br class="figure-break" /></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="Java-Broker-Concepts-Exchanges-Types-Headers"></a>4.3.2.4.&#160;Headers</h4></div></div></div><p>The headers exchange type routes messages to queues based on header properties within the message. The message is passed to
+    binding argument specifying a JMS message selector</a>.</p><div class="figure"><a id="idp428560"></a><p class="title"><strong>Figure&#160;4.7.&#160;Fanout exchange</strong></p><div class="figure-contents"><div class="mediaobject"><img alt="Fanout exchange" src="images/Exchange-Fanout.png" /></div></div></div><br class="figure-break" /></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="Java-Broker-Concepts-Exchanges-Types-Headers"></a>4.3.2.4.&#160;Headers</h4></div></div></div><p>The headers exchange type routes messages to queues based on header properties within the message. The message is passed to
      a queue if the header properties of the message satisfy the <a class="link" href="Java-Broker-Concepts-Exchanges.html#Java-Broker-Concepts-Exchanges-BindingArguments-x-match" title="4.3.3.2.&#160;x-match">
      x-match expression</a> specified by the binding arguments with which the queue was bound.
    </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="Java-Broker-Concepts-Exchanges-BindingArguments"></a>4.3.3.&#160;Binding Arguments</h3></div></div></div><p>Binding arguments are used by certain exchange types to further filter messages.</p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="Java-Broker-Concepts-Exchanges-BindingArguments-JMSSelector"></a>4.3.3.1.&#160;JMS Selector</h4></div></div></div><p>The binding argument <code class="literal">x-filter-jms-selector</code> specifies a JMS selector conditional expression. The expression
     is written in terms of message header and message property names.  If the expression evaluates to true, the message is routed to the queue.
-    This type of binding argument is understood by exchange types direct, topic and fanout.<a class="footnote" href="#ftn.idm140218887540544" id="idm140218887540544"><sup class="footnote">[4]</sup></a>.</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="Java-Broker-Concepts-Exchanges-BindingArguments-x-match"></a>4.3.3.2.&#160;x-match</h4></div></div></div><p>The binding argument <code class="literal">x-match</code> is understood by exchange type headers.  It can take two values, dictating how the
+    This type of binding argument is understood by exchange types direct, topic and fanout.<a class="footnote" href="#ftn.idp438064" id="idp438064"><sup class="footnote">[4]</sup></a>.</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="Java-Broker-Concepts-Exchanges-BindingArguments-x-match"></a>4.3.3.2.&#160;x-match</h4></div></div></div><p>The binding argument <code class="literal">x-match</code> is understood by exchange type headers.  It can take two values, dictating how the
     rest of the name value pairs are treated during matching.</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><code class="literal">all</code> implies that all the other pairs must match the headers property of a message for that message to be routed
       (i.e. an AND match)</li><li class="listitem">any<code class="literal" /> implies that the message should be routed if any of the fields in the headers property match one of the
       fields in the arguments table (i.e. an OR match)</li></ul></div><p>A field in the bind arguments matches a field in the message if either the field in the bind arguments has no value and a field of the
@@ -161,7 +161,7 @@
     The alternate exchange routes the message according to its routing algorithm and its binding table.  If the messages is still unroutable,
     the message is discarded.</li><li class="listitem">If using AMQP protocols 0-8..0-9-1, and the publisher set the mandatory flag and the<a class="link" href="Java-Broker-Close-Connection-When-No-Route.html" title="12.6.&#160;Closing client connections on unroutable mandatory messages">
      close when no route</a> feature did not close the connection, the message is returned to the Producer.</li><li class="listitem">Otherwise, the message is discarded.</li></ul></div><p>
-  </p></div><div class="footnotes"><br /><hr align="left" width="100" /><div class="footnote" id="ftn.idm140218887540544"><p><a class="para" href="#idm140218887540544"><sup class="para">[4] </sup></a>
+  </p></div><div class="footnotes"><br /><hr align="left" width="100" /><div class="footnote" id="ftn.idp438064"><p><a class="para" href="#idp438064"><sup class="para">[4] </sup></a>
     This is a Qpid specific extension.</p></div></div></div><div class="navfooter"><hr /><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="Java-Broker-Concepts-Virtual-Hosts.html">Prev</a>&#160;</td><td align="center" width="20%"><a accesskey="u" href="Java-Broker-Concepts.html">Up</a></td><td align="right" width="40%">&#160;<a accesskey="n" href="Java-Broker-Concepts-Queues.html">Next</a></td></tr><tr><td align="left" valign="top" width="40%">4.2.&#160;Virtual Hosts&#160;</td><td align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td align="right" valign="top" width="40%">&#160;4.4.&#160;Queues</td></tr></table></div></div>
 
         <hr/>

Modified: qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Concepts-Virtual-Hosts.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Concepts-Virtual-Hosts.html?rev=1576538&r1=1576537&r2=1576538&view=diff
==============================================================================
--- qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Concepts-Virtual-Hosts.html (original)
+++ qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Concepts-Virtual-Hosts.html Tue Mar 11 22:52:42 2014
@@ -113,7 +113,7 @@ and associated objects. Client <span cla
 with one being configured as the default for clients that can't or don't specify which they wish to connect to.
 </p><p>
     The following diagram depicts the Virtual Host model:
-    </p><div class="figure"><a id="idm140218887695904"></a><p class="title"><strong>Figure&#160;4.2.&#160;Virtual Host Model</strong></p><div class="figure-contents"><div class="mediaobject"><img alt="Virtual Host Model" src="images/VirtualHost-Model.png" /></div></div></div><p><br class="figure-break" />
+    </p><div class="figure"><a id="idp284976"></a><p class="title"><strong>Figure&#160;4.2.&#160;Virtual Host Model</strong></p><div class="figure-contents"><div class="mediaobject"><img alt="Virtual Host Model" src="images/VirtualHost-Model.png" /></div></div></div><p><br class="figure-break" />
 </p><p>Each <span class="emphasis"><em>Virtual Host</em></span> has its own <span class="emphasis"><em>Message Store</em></span> which is used to store persistent
 messages on durable <span class="emphasis"><em>Queues</em></span> it contains, as well as the configuration of any durable
 <span class="emphasis"><em>Queues</em></span>, <span class="emphasis"><em>Exchanges</em></span>, and <span class="emphasis"><em>Bindings</em></span> made during its operation.</p><p>

Modified: qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Concepts.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Concepts.html?rev=1576538&r1=1576537&r2=1576538&view=diff
==============================================================================
--- qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Concepts.html (original)
+++ qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Concepts.html Tue Mar 11 22:52:42 2014
@@ -116,7 +116,7 @@
         also provides management plugins to allow configuring and monitoring it.
         </p><p>
         The following diagram depicts the Broker model:
-        </p><div class="figure"><a id="idm140218887705536"></a><p class="title"><strong>Figure&#160;4.1.&#160;Broker Model</strong></p><div class="figure-contents"><div class="mediaobject"><img alt="Broker Model" src="images/Broker-Model.png" /></div></div></div><p><br class="figure-break" />
+        </p><div class="figure"><a id="idp307936"></a><p class="title"><strong>Figure&#160;4.1.&#160;Broker Model</strong></p><div class="figure-contents"><div class="mediaobject"><img alt="Broker Model" src="images/Broker-Model.png" /></div></div></div><p><br class="figure-break" />
         These concepts will be expanded upon in the forthcoming pages.
         </p></div></div><div class="navfooter"><hr /><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="Java-Broker-Getting-Started-CommandLine.html">Prev</a>&#160;</td><td align="center" width="20%">&#160;</td><td align="right" width="40%">&#160;<a accesskey="n" href="Java-Broker-Concepts-Virtual-Hosts.html">Next</a></td></tr><tr><td align="left" valign="top" width="40%">3.5.&#160;Using the command line&#160;</td><td align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td align="right" valign="top" width="40%">&#160;4.2.&#160;Virtual Hosts</td></tr></table></div></div>
 

Modified: qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Configuring-And-Managing-HTTP-Management.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Configuring-And-Managing-HTTP-Management.html?rev=1576538&r1=1576537&r2=1576538&view=diff
==============================================================================
--- qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Configuring-And-Managing-HTTP-Management.html (original)
+++ qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Configuring-And-Managing-HTTP-Management.html Tue Mar 11 22:52:42 2014
@@ -131,7 +131,7 @@
             instance although it is still evolving toward being fully considered a seperately supported interface.
         </p><p>The brokers REST interface support traditional REST model which uses the GET method requests to retrieve
             the information about broker configured objects, DELETE method requests to delete the configured object,
-            PUT to create or update the configured object and POST to perform the configured objects updates not available with the PUT requests.</p><p>The table below lists the available REST services with brief description how they can be used.</p><div class="table"><a id="idm140218887297152"></a><p class="title"><strong>Table&#160;5.2.&#160;Rest services</strong></p><div class="table-contents"><table border="1" summary="Rest services"><colgroup><col /><col /><col /><col /><col /><col /></colgroup><thead><tr><th>REST Service URL</th><th>Description</th><th>GET</th><th>PUT</th><th>POST</th><th>DELETE</th></tr></thead><tbody><tr><td><p>/rest/broker</p></td><td><p>Rest service to manage broker instance</p></td><td><p>Retrieves the details of broker configuration</p></td><td><p>Updates broker attributes</p></td><td><p>Not implemented yet</p></td><td><p>Not implemented yet</p></td></tr><tr><td><p>/rest/authenticationprovider</p>
+            PUT to create or update the configured object and POST to perform the configured objects updates not available with the PUT requests.</p><p>The table below lists the available REST services with brief description how they can be used.</p><div class="table"><a id="idp684528"></a><p class="title"><strong>Table&#160;5.2.&#160;Rest services</strong></p><div class="table-contents"><table border="1" summary="Rest services"><colgroup><col /><col /><col /><col /><col /><col /></colgroup><thead><tr><th>REST Service URL</th><th>Description</th><th>GET</th><th>PUT</th><th>POST</th><th>DELETE</th></tr></thead><tbody><tr><td><p>/rest/broker</p></td><td><p>Rest service to manage broker instance</p></td><td><p>Retrieves the details of broker configuration</p></td><td><p>Updates broker attributes</p></td><td><p>Not implemented yet</p></td><td><p>Not implemented yet</p></td></tr><tr><td><p>/rest/authenticationprovider</p>
                   <p>/rest/authenticationprovider/&lt;authentication provider name&gt;</p>
               </td><td>Rest service to manage authentication providers on the broker</td><td>Retrieves the details about authentication providers</td><td>Creates or updates authentication providers</td><td>Not implemented yet</td><td>Deletes authentication providers</td></tr><tr><td><p>/rest/user</p>
                   <p>/rest/user/&lt;authentication provider name&gt;/&lt;user name&gt;</p>
@@ -185,12 +185,12 @@
         If <span class="emphasis"><em>&lt;binding&gt;</em></span> and <span class="emphasis"><em>&lt;queue&gt;</em></span> are omitted in binding REST URL
         (http://localhost:8080/rest/binding/&lt;vhostname&gt;/&lt;exchangename&gt;) the GET request will result in returning 
         all bindings for all queues for the given exchange in the virtual host.
-        </p><div class="example"><a id="idm140218887206976"></a><p class="title"><strong>Example&#160;5.2.&#160;Examples of queue creation using curl (authenticating as user admin):</strong></p><div class="example-contents"><pre class="programlisting">
+        </p><div class="example"><a id="idp774704"></a><p class="title"><strong>Example&#160;5.2.&#160;Examples of queue creation using curl (authenticating as user admin):</strong></p><div class="example-contents"><pre class="programlisting">
 #create a durable queue
 curl --user admin -X PUT  -d '{"durable":true}' http://localhost:8080/rest/queue/&lt;vhostname&gt;/&lt;queuename&gt;
 #create a durable priority queue
 curl --user admin -X PUT  -d '{"durable":true,"type":"priority"}' http://localhost:8080/rest/queue/&lt;vhostname&gt;/&lt;queuename&gt;
-            </pre></div></div><br class="example-break" /><div class="example"><a id="idm140218887205456"></a><p class="title"><strong>Example&#160;5.3.&#160;Example of binding a queue to an exchange using curl</strong></p><div class="example-contents"><pre class="programlisting">
+            </pre></div></div><br class="example-break" /><div class="example"><a id="idp776224"></a><p class="title"><strong>Example&#160;5.3.&#160;Example of binding a queue to an exchange using curl</strong></p><div class="example-contents"><pre class="programlisting">
 curl --user admin -X PUT  -d '{}' http://localhost:8080/rest/binding/&lt;vhostname&gt;/&lt;exchangename&gt;/&lt;queue-name&gt;/&lt;binding-name&gt;
             </pre></div></div><br class="example-break" /><p>
             NOTE: These curl examples utilise unsecure HTTP transport. To use the examples it is first necessary enable Basic

Modified: qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Configuring-And-Managing.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Configuring-And-Managing.html?rev=1576538&r1=1576537&r2=1576538&view=diff
==============================================================================
--- qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Configuring-And-Managing.html (original)
+++ qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-Configuring-And-Managing.html Tue Mar 11 22:52:42 2014
@@ -192,7 +192,7 @@ $ ./qpid-server -st memory
             If both are defined, System Property values take precedence.
         </p><p>
             The broker has the following set of core configuration properties, with the indicated default values if not otherwise configured by the user:
-            </p><div class="table"><a id="idm140218887453104"></a><p class="title"><strong>Table&#160;5.1.&#160;Base Configuration Properties</strong></p><div class="table-contents"><table border="1" summary="Base Configuration Properties"><colgroup><col /><col /><col /></colgroup><thead><tr><th>
+            </p><div class="table"><a id="idp590832"></a><p class="title"><strong>Table&#160;5.1.&#160;Base Configuration Properties</strong></p><div class="table-contents"><table border="1" summary="Base Configuration Properties"><colgroup><col /><col /><col /></colgroup><thead><tr><th>
 	                        Name
                         </th><th>
 	                        Description
@@ -257,7 +257,7 @@ $ ./qpid-server -prop "qpid.amqp_port=10
         </p><p>
             NOTE: When running the broker on Windows and starting it via the qpid-server.bat file, the "name=value" argument MUST be quoted.
         </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="Java-Broker-Configuring-And-Managing-Configuration-Initial-Config-Example"></a>5.1.8.&#160;Example of JSON 'Initial Configuration'</h3></div></div></div><p>
-            An example of the default 'Initial Configuration' JSON file the broker uses is provided below:</p><div class="example"><a id="idm140218887339232"></a><p class="title"><strong>Example&#160;5.1.&#160;JSON 'Initial configuration' File</strong></p><div class="example-contents"><pre class="programlisting">
+            An example of the default 'Initial Configuration' JSON file the broker uses is provided below:</p><div class="example"><a id="idp616448"></a><p class="title"><strong>Example&#160;5.1.&#160;JSON 'Initial configuration' File</strong></p><div class="example-contents"><pre class="programlisting">
 {
   "name" : "Broker",
   "defaultVirtualHost" : "default",

Modified: qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-Backup.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-Backup.html?rev=1576538&r1=1576537&r2=1576538&view=diff
==============================================================================
--- qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-Backup.html (original)
+++ qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-Backup.html Tue Mar 11 22:52:42 2014
@@ -109,8 +109,8 @@
         <ul id="-path-navigation"><li><a href="/releases/index.html">Releases</a></li><li><a href="/releases/qpid-0.26/index.html">Qpid 0.26</a></li><li><a href="/releases/qpid-0.26/java-broker/book/index.html">AMQP Messaging Broker (Java)</a></li><li>13.13.&#160;Backups</li></ul>
         <div class="docbook"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">13.13.&#160;Backups</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="Java-Broker-High-Availability-Security.html">Prev</a>&#160;</td><th align="center" width="60%">Chapter&#160;13.&#160;High Availability</th><td align="right" width="20%">&#160;<a accesskey="n" href="Java-Broker-High-Availability-MigrationFromNonHA.html">Next</a></td></tr></table><hr /></div><div class="section"><div class="titlepage"><div><div><h2 class="title"><a id="Java-Broker-High-Availability-Backup"></a>13.13.&#160;Backups</h2></div></div></div><p>In order to protect the entire cluster from some cataclysms which might destroy all cluster nodes,
     backups of the Master store should be taken on a regular basis.</p><p>Qpid Broker distribution includes the "hot" backup utility <span class="emphasis"><em>backup.sh</em></span> which can be found at broker bin folder.
-         This utility can perform the backup when broker is running.</p><p><span class="emphasis"><em>backup.sh</em></span> script invokes <code class="classname">org.apache.qpid.server.store.berkeleydb.BDBBackup</code> to do the job.</p><p>You can also run this class from command line like in an example below:</p><div class="example"><a id="idm140218886157056"></a><p class="title"><strong>Example&#160;13.5.&#160;Performing store backup by using <code class="classname">BDBBackup</code> class directly</strong></p><div class="example-contents"><span class="command"><strong>
-        java -cp qpid-bdbstore-0.18.jar org.apache.qpid.server.store.berkeleydb.BDBBackup -fromdir path/to/store/folder -todir path/to/backup/foldeAr</strong></span></div></div><br class="example-break" /><p>In the example above BDBBackup utility is called from qpid-bdbstore-0.18.jar to backup the store at <span class="emphasis"><em>path/to/store/folder</em></span> and copy store logs into <span class="emphasis"><em>path/to/backup/folder</em></span>.</p><p>Linux and Unix users can take advantage of <span class="emphasis"><em>backup.sh</em></span> bash script by running this script in a similar way.</p><div class="example"><a id="idm140218886153040"></a><p class="title"><strong>Example&#160;13.6.&#160;Performing store backup by using <code class="classname">backup.sh</code> bash script</strong></p><div class="example-contents"><span class="command"><strong>backup.sh -fromdir path/to/store/folder -todir path/to/backup/folder</strong></span></div></div><br class="example-break" /><div 
 class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Do not forget to ensure that the Master store is being backed up, in the event the Node elected Master changes during
+         This utility can perform the backup when broker is running.</p><p><span class="emphasis"><em>backup.sh</em></span> script invokes <code class="classname">org.apache.qpid.server.store.berkeleydb.BDBBackup</code> to do the job.</p><p>You can also run this class from command line like in an example below:</p><div class="example"><a id="idp1829280"></a><p class="title"><strong>Example&#160;13.5.&#160;Performing store backup by using <code class="classname">BDBBackup</code> class directly</strong></p><div class="example-contents"><span class="command"><strong>
+        java -cp qpid-bdbstore-0.18.jar org.apache.qpid.server.store.berkeleydb.BDBBackup -fromdir path/to/store/folder -todir path/to/backup/foldeAr</strong></span></div></div><br class="example-break" /><p>In the example above BDBBackup utility is called from qpid-bdbstore-0.18.jar to backup the store at <span class="emphasis"><em>path/to/store/folder</em></span> and copy store logs into <span class="emphasis"><em>path/to/backup/folder</em></span>.</p><p>Linux and Unix users can take advantage of <span class="emphasis"><em>backup.sh</em></span> bash script by running this script in a similar way.</p><div class="example"><a id="idp1833296"></a><p class="title"><strong>Example&#160;13.6.&#160;Performing store backup by using <code class="classname">backup.sh</code> bash script</strong></p><div class="example-contents"><span class="command"><strong>backup.sh -fromdir path/to/store/folder -todir path/to/backup/folder</strong></span></div></div><br class="example-break" /><div class="n
 ote" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Do not forget to ensure that the Master store is being backed up, in the event the Node elected Master changes during
       the lifecycle of the cluster.</p></div></div><div class="navfooter"><hr /><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="Java-Broker-High-Availability-Security.html">Prev</a>&#160;</td><td align="center" width="20%"><a accesskey="u" href="Java-Broker-High-Availability.html">Up</a></td><td align="right" width="40%">&#160;<a accesskey="n" href="Java-Broker-High-Availability-MigrationFromNonHA.html">Next</a></td></tr><tr><td align="left" valign="top" width="40%">13.12.&#160;Security&#160;</td><td align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td align="right" valign="top" width="40%">&#160;13.14.&#160;Migration of a non-HA store to HA</td></tr></table></div></div>
 
         <hr/>

Modified: qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-ClientFailover.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-ClientFailover.html?rev=1576538&r1=1576537&r2=1576538&view=diff
==============================================================================
--- qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-ClientFailover.html (original)
+++ qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-ClientFailover.html Tue Mar 11 22:52:42 2014
@@ -114,7 +114,7 @@
       The recommended value for <span class="emphasis"><em>connectdelay</em></span> option in broker URL should be set to
       the value greater than 1000 milliseconds. If it is desired that clients re-connect automatically after a
       master to replica failure, <code class="varname">cyclecount</code> should be tuned so that the retry period is longer than
-      the expected length of time to perform the failover.</p><div class="example"><a id="idm140218886247968"></a><p class="title"><strong>Example&#160;13.2.&#160;Example of connection URL for the HA Cluster</strong></p><div class="example-contents">
+      the expected length of time to perform the failover.</p><div class="example"><a id="idp1738368"></a><p class="title"><strong>Example&#160;13.2.&#160;Example of connection URL for the HA Cluster</strong></p><div class="example-contents">
 amqp://guest:guest@clientid/test?brokerlist='tcp://localhost:5672?connectdelay='2000'&amp;retries='3';tcp://localhost:5671?connectdelay='2000'&amp;retries='3';tcp://localhost:5673?connectdelay='2000'&amp;retries='3''&amp;failover='roundrobin?cyclecount='30''
         </div></div><br class="example-break" /></div><div class="navfooter"><hr /><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="Java-Broker-High-Availability-DurabilityGuarantee.html">Prev</a>&#160;</td><td align="center" width="20%"><a accesskey="u" href="Java-Broker-High-Availability.html">Up</a></td><td align="right" width="40%">&#160;<a accesskey="n" href="Java-Broker-High-Availability-JMXAPI.html">Next</a></td></tr><tr><td align="left" valign="top" width="40%">13.6.&#160;Durability Guarantees&#160;</td><td align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td align="right" valign="top" width="40%">&#160;13.8.&#160;Qpid JMX API for HA</td></tr></table></div></div>
 

Modified: qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-Configuration.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-Configuration.html?rev=1576538&r1=1576537&r2=1576538&view=diff
==============================================================================
--- qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-Configuration.html (original)
+++ qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-Configuration.html Tue Mar 11 22:52:42 2014
@@ -109,7 +109,7 @@
         <ul id="-path-navigation"><li><a href="/releases/index.html">Releases</a></li><li><a href="/releases/qpid-0.26/index.html">Qpid 0.26</a></li><li><a href="/releases/qpid-0.26/java-broker/book/index.html">AMQP Messaging Broker (Java)</a></li><li>13.5.&#160;Configuring a Virtual Host to be a node</li></ul>
         <div class="docbook"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">13.5.&#160;Configuring a Virtual Host to be a node</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="Java-Broker-High-Availability-MultiNodeCluster.html">Prev</a>&#160;</td><th align="center" width="60%">Chapter&#160;13.&#160;High Availability</th><td align="right" width="20%">&#160;<a accesskey="n" href="Java-Broker-High-Availability-DurabilityGuarantee.html">Next</a></td></tr></table><hr /></div><div class="section"><div class="titlepage"><div><div><h2 class="title"><a id="Java-Broker-High-Availability-Configuration"></a>13.5.&#160;Configuring a Virtual Host to be a node</h2></div></div></div><p>To configure a virtualhost as a cluster node, configure the virtualhost.xml in the following manner:</p><p>
 
-    </p><div class="example"><a id="idm140218886320112"></a><p class="title"><strong>Example&#160;13.1.&#160;Configuring a VirtualHost to use the BDBHAMessageStore</strong></p><div class="example-contents"><pre class="programlisting">
+    </p><div class="example"><a id="idp1666144"></a><p class="title"><strong>Example&#160;13.1.&#160;Configuring a VirtualHost to use the BDBHAMessageStore</strong></p><div class="example-contents"><pre class="programlisting">
 &lt;virtualhosts&gt;
   &lt;virtualhost&gt;
     &lt;name&gt;vhostname&lt;/name&gt;

Modified: qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-DisasterRecovery.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-DisasterRecovery.html?rev=1576538&r1=1576537&r2=1576538&view=diff
==============================================================================
--- qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-DisasterRecovery.html (original)
+++ qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-DisasterRecovery.html Tue Mar 11 22:52:42 2014
@@ -112,7 +112,7 @@
     In case when HA message store needs to be restored on a different host with a different IP address
     the cluster replication configuration should be reseted in this case</p><p>Oracle provides a command line utility <a class="ulink" href="http://docs.oracle.com/cd/E17277_02/html/java/com/sleepycat/je/rep/util/DbResetRepGroup.html" target="_top"><code class="classname">DbResetRepGroup</code></a>
     to reset the members of a replication group and replace the group with a new group consisting of a single new member
-    as described by the arguments supplied to the utility</p><p>Cluster can be restored with the following steps:</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Copy log files into the store folder from backup</p></li><li class="listitem"><p>Use <code class="classname">DbResetRepGroup</code> to reset an existing environment. See an example below</p><div class="example"><a id="idm140218886130368"></a><p class="title"><strong>Example&#160;13.9.&#160;Reseting of replication group with <code class="classname">DbResetRepGroup</code></strong></p><div class="example-contents"><span class="command"><strong>
+    as described by the arguments supplied to the utility</p><p>Cluster can be restored with the following steps:</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Copy log files into the store folder from backup</p></li><li class="listitem"><p>Use <code class="classname">DbResetRepGroup</code> to reset an existing environment. See an example below</p><div class="example"><a id="idp1855968"></a><p class="title"><strong>Example&#160;13.9.&#160;Reseting of replication group with <code class="classname">DbResetRepGroup</code></strong></p><div class="example-contents"><span class="command"><strong>
 java -cp je-5.0.97.jar com.sleepycat.je.rep.util.DbResetRepGroup -h ha-work/Node-5001/bdbstore -groupName TestClusterGroup -nodeName Node-5001 -nodeHostPort localhost:5001</strong></span></div></div><br class="example-break" /><p>In the example above <code class="classname">DbResetRepGroup</code> utility from Berkeley JE of version 5.0.97 is used to reset the store
             at location <span class="emphasis"><em>ha-work/Node-5001/bdbstore</em></span> and set a replication group to <span class="emphasis"><em>TestClusterGroup</em></span>
             having a node <span class="emphasis"><em>Node-5001</em></span> which runs at <span class="emphasis"><em>localhost:5001</em></span>.</p></li><li class="listitem"><p>Start a broker with HA store configured as specified on running of <code class="classname">DbResetRepGroup</code> utility.</p></li><li class="listitem"><p>Start replica nodes having the same replication group and a helper host port pointing to a new master. The store content will be copied into Replicas from Master on their start up.</p></li></ul></div></div><div class="navfooter"><hr /><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="Java-Broker-High-Availability-MigrationFromNonHA.html">Prev</a>&#160;</td><td align="center" width="20%"><a accesskey="u" href="Java-Broker-High-Availability.html">Up</a></td><td align="right" width="40%">&#160;<a accesskey="n" href="Java-Broker-High-Availability-Performance.html">Next</a></td></tr><tr><td align="left" valign
 ="top" width="40%">13.14.&#160;Migration of a non-HA store to HA&#160;</td><td align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td align="right" valign="top" width="40%">&#160;13.16.&#160;Performance</td></tr></table></div></div>

Modified: qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-DurabilityGuarantee.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-DurabilityGuarantee.html?rev=1576538&r1=1576537&r2=1576538&view=diff
==============================================================================
--- qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-DurabilityGuarantee.html (original)
+++ qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-DurabilityGuarantee.html Tue Mar 11 22:52:42 2014
@@ -131,7 +131,7 @@
          of this combination is described in the table below. It offers a good compromise between durability guarantee and performance
          with writes being guaranteed on the master and the additional guarantee that a majority of replicas have received the
          transaction.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="Java-Broker-High-Availability-DurabilityGuarantee_Examples"></a>13.6.4.&#160;Examples</h3></div></div></div><p>Here are some examples illustrating the effects of the durability and coalescing-sync settings.</p><p>
-        </p><div class="table"><a id="idm140218886268976"></a><p class="title"><strong>Table&#160;13.1.&#160;Effect of different durability guarantees</strong></p><div class="table-contents"><table border="1" summary="Effect of different durability guarantees"><colgroup><col /><col /><col /><col /></colgroup><thead><tr><th>&#160;</th><th>Durability</th><th>Coalescing-sync</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>NO_SYNC, NO_SYNC, SIMPLE_MAJORITY</td><td>true</td><td>Before the commit returns to the client, the transaction will be written/sync'd to the Master's disk (effect of
+        </p><div class="table"><a id="idp1717360"></a><p class="title"><strong>Table&#160;13.1.&#160;Effect of different durability guarantees</strong></p><div class="table-contents"><table border="1" summary="Effect of different durability guarantees"><colgroup><col /><col /><col /><col /></colgroup><thead><tr><th>&#160;</th><th>Durability</th><th>Coalescing-sync</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>NO_SYNC, NO_SYNC, SIMPLE_MAJORITY</td><td>true</td><td>Before the commit returns to the client, the transaction will be written/sync'd to the Master's disk (effect of
                    coalescing-sync) and a majority of the replica(s) will have acknowledged the <span class="bold"><strong>receipt</strong></span>
                    of the transaction.  The replicas will write and sync the transaction to their disk at a point in the future governed by
                    <a class="ulink" href="http://docs.oracle.com/cd/E17277_02/html/java/com/sleepycat/je/rep/ReplicationMutableConfig.html#LOG_FLUSH_TASK_INTERVAL" target="_top">ReplicationMutableConfig#LOG_FLUSH_INTERVAL</a>.

Modified: qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-JMXAPI.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-JMXAPI.html?rev=1576538&r1=1576537&r2=1576538&view=diff
==============================================================================
--- qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-JMXAPI.html (original)
+++ qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-JMXAPI.html Tue Mar 11 22:52:42 2014
@@ -178,7 +178,7 @@
           </td>
           <td>void</td>
           <td>Update the address of another node. The node must be in a STOPPED state.</td>
-        </tr></tbody></table></div><div class="figure"><a id="idm140218886203216"></a><p class="title"><strong>Figure&#160;13.7.&#160;BDBHAMessageStore view from jconsole.</strong></p><div class="figure-contents"><div><img alt="BDBHAMessageStore view from jconsole." src="images/HA-BDBHAMessageStore-MBean-jconsole.png" /></div></div></div><br class="figure-break" /><div class="example"><a id="idm140218886201712"></a><p class="title"><strong>Example&#160;13.3.&#160;Example of java code to get the node state value</strong></p><div class="example-contents"><pre class="programlisting">
+        </tr></tbody></table></div><div class="figure"><a id="idp1783120"></a><p class="title"><strong>Figure&#160;13.7.&#160;BDBHAMessageStore view from jconsole.</strong></p><div class="figure-contents"><div><img alt="BDBHAMessageStore view from jconsole." src="images/HA-BDBHAMessageStore-MBean-jconsole.png" /></div></div></div><br class="figure-break" /><div class="example"><a id="idp1784624"></a><p class="title"><strong>Example&#160;13.3.&#160;Example of java code to get the node state value</strong></p><div class="example-contents"><pre class="programlisting">
 Map&lt;String, Object&gt; environment = new HashMap&lt;String, Object&gt;();
 
 // credentials: user name and password

Modified: qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-MigrationFromNonHA.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-MigrationFromNonHA.html?rev=1576538&r1=1576537&r2=1576538&view=diff
==============================================================================
--- qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-MigrationFromNonHA.html (original)
+++ qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-MigrationFromNonHA.html Tue Mar 11 22:52:42 2014
@@ -107,10 +107,10 @@
 
       <div id="-middle" class="panel">
         <ul id="-path-navigation"><li><a href="/releases/index.html">Releases</a></li><li><a href="/releases/qpid-0.26/index.html">Qpid 0.26</a></li><li><a href="/releases/qpid-0.26/java-broker/book/index.html">AMQP Messaging Broker (Java)</a></li><li>13.14.&#160;Migration of a non-HA store to HA</li></ul>
-        <div class="docbook"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">13.14.&#160;Migration of a non-HA store to HA</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="Java-Broker-High-Availability-Backup.html">Prev</a>&#160;</td><th align="center" width="60%">Chapter&#160;13.&#160;High Availability</th><td align="right" width="20%">&#160;<a accesskey="n" href="Java-Broker-High-Availability-DisasterRecovery.html">Next</a></td></tr></table><hr /></div><div class="section"><div class="titlepage"><div><div><h2 class="title"><a id="Java-Broker-High-Availability-MigrationFromNonHA"></a>13.14.&#160;Migration of a non-HA store to HA</h2></div></div></div><p>Non HA stores starting from schema version 4 (0.14 Qpid release) can be automatically converted into HA store on broker startup if replication is first enabled with the <a class="ulink" href="http://docs.oracle.com/cd/E17277_02/html/java/com/sleepycat/je/rep/u
 til/DbEnableReplication.html" target="_top"><code class="classname">DbEnableReplication</code></a> utility from the BDB JE jar.</p><p>DbEnableReplication converts a non HA store into an HA store and can be used as follows:</p><div class="example"><a id="idm140218886147008"></a><p class="title"><strong>Example&#160;13.7.&#160;Enabling replication</strong></p><div class="example-contents"><span class="command"><strong>
+        <div class="docbook"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">13.14.&#160;Migration of a non-HA store to HA</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="Java-Broker-High-Availability-Backup.html">Prev</a>&#160;</td><th align="center" width="60%">Chapter&#160;13.&#160;High Availability</th><td align="right" width="20%">&#160;<a accesskey="n" href="Java-Broker-High-Availability-DisasterRecovery.html">Next</a></td></tr></table><hr /></div><div class="section"><div class="titlepage"><div><div><h2 class="title"><a id="Java-Broker-High-Availability-MigrationFromNonHA"></a>13.14.&#160;Migration of a non-HA store to HA</h2></div></div></div><p>Non HA stores starting from schema version 4 (0.14 Qpid release) can be automatically converted into HA store on broker startup if replication is first enabled with the <a class="ulink" href="http://docs.oracle.com/cd/E17277_02/html/java/com/sleepycat/je/rep/u
 til/DbEnableReplication.html" target="_top"><code class="classname">DbEnableReplication</code></a> utility from the BDB JE jar.</p><p>DbEnableReplication converts a non HA store into an HA store and can be used as follows:</p><div class="example"><a id="idp1839328"></a><p class="title"><strong>Example&#160;13.7.&#160;Enabling replication</strong></p><div class="example-contents"><span class="command"><strong>
 java -jar je-5.0.97.jar DbEnableReplication -h /path/to/store -groupName MyReplicationGroup -nodeName MyNode1 -nodeHostPort  localhost:5001
         </strong></span></div></div><br class="example-break" /><p>In the examples above, je jar of version 5.0.97 is used to convert store at <span class="emphasis"><em>/path/to/store</em></span> into HA store having replication group name <span class="emphasis"><em>MyReplicationGroup</em></span>, node name <span class="emphasis"><em>MyNode1</em></span> and running on host <span class="emphasis"><em>localhost</em></span> and port <span class="emphasis"><em>5001</em></span>.</p><p>After running DbEnableReplication and updating the virtual host store to configuration to be an HA message store, like in example below,
-    on broker start up the store schema will be upgraded to the most recent version and the broker can be used as normal.</p><div class="example"><a id="idm140218886142544"></a><p class="title"><strong>Example&#160;13.8.&#160;Example of XML configuration for HA message store</strong></p><div class="example-contents"><pre class="programlisting">
+    on broker start up the store schema will be upgraded to the most recent version and the broker can be used as normal.</p><div class="example"><a id="idp1843792"></a><p class="title"><strong>Example&#160;13.8.&#160;Example of XML configuration for HA message store</strong></p><div class="example-contents"><pre class="programlisting">
 &lt;store&gt;
     &lt;class&gt;org.apache.qpid.server.store.berkeleydb.BDBHAMessageStore&lt;/class&gt;
     &lt;environment-path&gt;/path/to/store&lt;/environment-path&gt;

Modified: qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-Monitoring-cluster.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-Monitoring-cluster.html?rev=1576538&r1=1576537&r2=1576538&view=diff
==============================================================================
--- qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-Monitoring-cluster.html (original)
+++ qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-Monitoring-cluster.html Tue Mar 11 22:52:42 2014
@@ -108,7 +108,7 @@
       <div id="-middle" class="panel">
         <ul id="-path-navigation"><li><a href="/releases/index.html">Releases</a></li><li><a href="/releases/qpid-0.26/index.html">Qpid 0.26</a></li><li><a href="/releases/qpid-0.26/java-broker/book/index.html">AMQP Messaging Broker (Java)</a></li><li>13.9.&#160;Monitoring cluster</li></ul>
         <div class="docbook"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">13.9.&#160;Monitoring cluster</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="Java-Broker-High-Availability-JMXAPI.html">Prev</a>&#160;</td><th align="center" width="60%">Chapter&#160;13.&#160;High Availability</th><td align="right" width="20%">&#160;<a accesskey="n" href="Java-Broker-High-Availability-DiskSpace.html">Next</a></td></tr></table><hr /></div><div class="section"><div class="titlepage"><div><div><h2 class="title"><a id="Java-Broker-High-Availability-Monitoring-cluster"></a>13.9.&#160;Monitoring cluster</h2></div></div></div><p>In order to discover potential issues with HA Cluster early, all nodes in the Cluster should be monitored on regular basis
-    using the following techniques:</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Broker log files scrapping for WARN or ERROR entries and operational log entries like:</p><div class="itemizedlist"><ul class="itemizedlist" type="circle"><li class="listitem"><p><span class="emphasis"><em>MST-1007 :</em></span> Store Passivated. It can indicate that Master virtual host has gone down.</p></li><li class="listitem"><p><span class="emphasis"><em>MST-1006 :</em></span> Recovery Complete. It can indicate that a former Replica virtual host is up and became the Master.</p></li></ul></div></li><li class="listitem"><p>Disk space usage and system load using system tools.</p></li><li class="listitem"><p>Berkeley HA node status using <a class="ulink" href="http://docs.oracle.com/cd/E17277_02/html/java/com/sleepycat/je/rep/util/DbPing.html" target="_top"><code class="classname">DbPing</code></a> utility.</p><div class="example"><a id="idm140218886189936">
 </a><p class="title"><strong>Example&#160;13.4.&#160;Using <code class="classname">DbPing</code> utility for monitoring HA nodes.</strong></p><div class="example-contents"><span class="command"><strong>
+    using the following techniques:</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Broker log files scrapping for WARN or ERROR entries and operational log entries like:</p><div class="itemizedlist"><ul class="itemizedlist" type="circle"><li class="listitem"><p><span class="emphasis"><em>MST-1007 :</em></span> Store Passivated. It can indicate that Master virtual host has gone down.</p></li><li class="listitem"><p><span class="emphasis"><em>MST-1006 :</em></span> Recovery Complete. It can indicate that a former Replica virtual host is up and became the Master.</p></li></ul></div></li><li class="listitem"><p>Disk space usage and system load using system tools.</p></li><li class="listitem"><p>Berkeley HA node status using <a class="ulink" href="http://docs.oracle.com/cd/E17277_02/html/java/com/sleepycat/je/rep/util/DbPing.html" target="_top"><code class="classname">DbPing</code></a> utility.</p><div class="example"><a id="idp1796400"></a><p c
 lass="title"><strong>Example&#160;13.4.&#160;Using <code class="classname">DbPing</code> utility for monitoring HA nodes.</strong></p><div class="example-contents"><span class="command"><strong>
 java -jar je-5.0.97.jar DbPing -groupName TestClusterGroup -nodeName Node-5001 -nodeHost localhost:5001 -socketTimeout 10000
 </strong></span><pre class="screen">
 Current state of node: Node-5001 from group: TestClusterGroup

Modified: qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-OfferingsOfJavaBroker.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-OfferingsOfJavaBroker.html?rev=1576538&r1=1576537&r2=1576538&view=diff
==============================================================================
--- qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-OfferingsOfJavaBroker.html (original)
+++ qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-OfferingsOfJavaBroker.html Tue Mar 11 22:52:42 2014
@@ -116,9 +116,9 @@
       the unit of replication.  The Active node (referred to as the <span class="bold"><strong>Master</strong></span>) accepts all work from all the clients.
        The Passive nodes (referred to as <span class="bold"><strong>Replicas</strong></span>) are unavailable for work: the only task they must perform is
        to remain in synch with the Master node by consuming a replication stream containing all data and state.</p><p>If the Master node fails, a Replica node is elected to become the new Master node.  All clients automatically failover
-      <a class="footnote" href="#ftn.idm140218887066704" id="idm140218887066704"><sup class="footnote">[5]</sup></a> to the new Master and continue their work.</p><p>The Java Broker HA solution is incompatible with the HA solution offered by the CPP Broker.  It is not possible to co-locate Java and CPP
+      <a class="footnote" href="#ftn.idp920640" id="idp920640"><sup class="footnote">[5]</sup></a> to the new Master and continue their work.</p><p>The Java Broker HA solution is incompatible with the HA solution offered by the CPP Broker.  It is not possible to co-locate Java and CPP
        Brokers within the same cluster.</p><p>HA is not currently available for those using the the <span class="bold"><strong>Derby Store</strong></span> or <span class="bold"><strong>Memory
-      Message Store</strong></span>.</p><div class="footnotes"><br /><hr align="left" width="100" /><div class="footnote" id="ftn.idm140218887066704"><p><a class="para" href="#idm140218887066704"><sup class="para">[5] </sup></a>The automatic failover feature is available only for AMQP connections from the Java client.  Management connections (JMX)
+      Message Store</strong></span>.</p><div class="footnotes"><br /><hr align="left" width="100" /><div class="footnote" id="ftn.idp920640"><p><a class="para" href="#idp920640"><sup class="para">[5] </sup></a>The automatic failover feature is available only for AMQP connections from the Java client.  Management connections (JMX)
         do not current offer this feature.</p></div></div></div><div class="navfooter"><hr /><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="Java-Broker-High-Availability.html">Prev</a>&#160;</td><td align="center" width="20%"><a accesskey="u" href="Java-Broker-High-Availability.html">Up</a></td><td align="right" width="40%">&#160;<a accesskey="n" href="Java-Broker-High-Availability-TwoNodeCluster.html">Next</a></td></tr><tr><td align="left" valign="top" width="40%">Chapter&#160;13.&#160;High Availability&#160;</td><td align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td align="right" valign="top" width="40%">&#160;13.3.&#160;Two Node Cluster</td></tr></table></div></div>
 
         <hr/>

Modified: qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-Performance.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-Performance.html?rev=1576538&r1=1576537&r2=1576538&view=diff
==============================================================================
--- qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-Performance.html (original)
+++ qpid/site/docs/releases/qpid-0.26/java-broker/book/Java-Broker-High-Availability-Performance.html Tue Mar 11 22:52:42 2014
@@ -211,7 +211,7 @@
           <td>-89.55%</td>
           <td>-89.55%</td>
           <td>-50.54%</td>
-        </tr></tbody></table></div><p>The figure below depicts the graphs for the performance test results</p><div class="figure"><a id="idm140218886060608"></a><p class="title"><strong>Figure&#160;13.8.&#160;Test results</strong></p><div class="figure-contents"><div><img alt="Test results" src="images/HA-perftests-results.png" /></div></div></div><br class="figure-break" /><p>On using durability <span class="emphasis"><em>SYNC,SYNC,ALL</em></span> (without coalescing-sync) the performance drops significantly (by 62-95%) in comparison with non HA broker.</p><p>Whilst, on using durability <span class="emphasis"><em>WRITE_NO_SYNC,WRITE_NO_SYNC,ALL</em></span> (without coalescing-sync) the performance drops by only half, but with loss of durability guarantee, so is not recommended.</p><p>In order to have better performance with HA, Qpid Broker comes up with the special mode called <a class="link" href="Java-Broker-High-Availability-DurabilityGuarantee.html#Java-Broker-High-Availability
 -DurabilityGuarantee_CoalescingSync" title="13.6.2.&#160;Coalescing-sync">coalescing-sync</a>,
+        </tr></tbody></table></div><p>The figure below depicts the graphs for the performance test results</p><div class="figure"><a id="idp1925728"></a><p class="title"><strong>Figure&#160;13.8.&#160;Test results</strong></p><div class="figure-contents"><div><img alt="Test results" src="images/HA-perftests-results.png" /></div></div></div><br class="figure-break" /><p>On using durability <span class="emphasis"><em>SYNC,SYNC,ALL</em></span> (without coalescing-sync) the performance drops significantly (by 62-95%) in comparison with non HA broker.</p><p>Whilst, on using durability <span class="emphasis"><em>WRITE_NO_SYNC,WRITE_NO_SYNC,ALL</em></span> (without coalescing-sync) the performance drops by only half, but with loss of durability guarantee, so is not recommended.</p><p>In order to have better performance with HA, Qpid Broker comes up with the special mode called <a class="link" href="Java-Broker-High-Availability-DurabilityGuarantee.html#Java-Broker-High-Availability-Durabil
 ityGuarantee_CoalescingSync" title="13.6.2.&#160;Coalescing-sync">coalescing-sync</a>,
     With this mode enabled, Qpid broker batches the concurrent transaction commits and syncs transaction data into Master disk in one go.
     As result, the HA performance only drops by 25-60% for durability <span class="emphasis"><em>NO_SYNC,NO_SYNC,ALL</em></span> and by 10-90% for <span class="emphasis"><em>WRITE_NO_SYNC,WRITE_NO_SYNC,ALL</em></span>.</p></div><div class="navfooter"><hr /><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="Java-Broker-High-Availability-DisasterRecovery.html">Prev</a>&#160;</td><td align="center" width="20%"><a accesskey="u" href="Java-Broker-High-Availability.html">Up</a></td><td align="right" width="40%">&#160;<a accesskey="n" href="Java-Broker-Virtual-Hosts-Configuration-File.html">Next</a></td></tr><tr><td align="left" valign="top" width="40%">13.15.&#160;Disaster Recovery&#160;</td><td align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td align="right" valign="top" width="40%">&#160;Chapter&#160;14.&#160;Virtual Host XML configuration file</td></tr></table></div></div>
 



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org


Mime
View raw message