You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@qpid.apache.org by kw...@apache.org on 2013/10/09 00:32:50 UTC
svn commit: r1530450 [2/4] -
/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/
Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-MigrationFromNonHA.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-MigrationFromNonHA.html?rev=1530450&r1=1530449&r2=1530450&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-MigrationFromNonHA.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-MigrationFromNonHA.html Tue Oct 8 22:32:49 2013
@@ -1,7 +1,7 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>13.14. Migration of a non-HA store to HA</title><link rel="stylesheet" type="text/css" href="css/style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="AMQP Messaging Broker (Java)"><link rel="up" href="Java-Broker-High-Availability.html" title="Chapter 13. High Availability"><link rel="prev" href="Java-Broker-High-Availability-Backup.html" title="13.13. Backups"><link rel="next" href="Java-Broker-High-Availability-DisasterRecovery.html" title="13.15. Disaster Recovery"></head><body><div class="container" bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><DIV class="header"><DIV class="logo"><H1>Apache Qpidâ¢</H1><H2>Open Source AMQP Messaging</H2></DIV></DIV><DIV class="menu_box"><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Apache Qpid</H3><UL><LI><A href="http://qpid.apach
e.org/index.html">Home</A></LI><LI><A href="http://qpid.apache.org/download.html">Download</A></LI><LI><A href="http://qpid.apache.org/getting_started.html">Getting Started</A></LI><LI><A href="http://www.apache.org/licenses/">License</A></LI><LI><A href="https://cwiki.apache.org/qpid/faq.html">FAQ</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Documentation</H3><UL><LI><A href="http://qpid.apache.org/documentation.html#doc-release">Latest Release</A></LI><LI><A href="http://qpid.apache.org/documentation.html#doc-trunk">Trunk</A></LI><LI><A href="http://qpid.apache.org/documentation.html#doc-archives">Archive</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Community</H3><UL><LI><A href="http://qpid.apache.org/getting_involved.html">Getting Involved</A></LI><LI><A href="http://qpid.apache.org/source_repository.html">Source Repository</A></LI><LI><
A href="http://qpid.apache.org/mailing_lists.html">Mailing Lists</A></LI><LI><A href="https://cwiki.apache.org/qpid/">Wiki</A></LI><LI><A href="https://issues.apache.org/jira/browse/qpid">Issue Reporting</A></LI><LI><A href="http://qpid.apache.org/people.html">People</A></LI><LI><A href="http://qpid.apache.org/acknowledgements.html">Acknowledgements</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Developers</H3><UL><LI><A href="https://cwiki.apache.org/qpid/building.html">Building Qpid</A></LI><LI><A href="https://cwiki.apache.org/qpid/developer-pages.html">Developer Pages</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>About AMQP</H3><UL><LI><A href="http://qpid.apache.org/amqp.html">What is AMQP?</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>About Apache</H3><UL><LI><A href="
http://www.apache.org">Home</A></LI><LI><A href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</A></LI><LI><A href="http://www.apache.org/foundation/thanks.html">Thanks</A></LI><LI><A href="http://www.apache.org/security/">Security</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV></DIV><div class="main_text_area"><div class="main_text_area_top"></div><div class="main_text_area_body"><DIV class="breadcrumbs"><span class="breadcrumb-link"><a href="index.html">AMQP Messaging Broker (Java)</a></span> > <span class="breadcrumb-link"><a href="Java-Broker-High-Availability.html">High Availability</a></span> > <span class="breadcrumb-node">Migration of a non-HA store to HA</span></DIV><div class="section"><div class="titlepage"><div><div><h2 class="title"><a name="Java-Broker-High-Availability-MigrationFromNonHA"></a>13.14. 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 automat
ically 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/util/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 name="idp8364928"></a><p class="title"><b>Example 13.7. Enabling replication</b></p><div class="example-contents"><span class="command"><strong>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>13.14. Migration of a non-HA store to HA</title><link rel="stylesheet" type="text/css" href="css/style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="AMQP Messaging Broker (Java)"><link rel="up" href="Java-Broker-High-Availability.html" title="Chapter 13. High Availability"><link rel="prev" href="Java-Broker-High-Availability-Backup.html" title="13.13. Backups"><link rel="next" href="Java-Broker-High-Availability-DisasterRecovery.html" title="13.15. Disaster Recovery"></head><body><div class="container" bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><DIV class="header"><DIV class="logo"><H1>Apache Qpidâ¢</H1><H2>Open Source AMQP Messaging</H2></DIV></DIV><DIV class="menu_box"><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Apache Qpid</H3><UL><LI><A href="http://qpid.apach
e.org/index.html">Home</A></LI><LI><A href="http://qpid.apache.org/download.html">Download</A></LI><LI><A href="http://qpid.apache.org/getting_started.html">Getting Started</A></LI><LI><A href="http://www.apache.org/licenses/">License</A></LI><LI><A href="https://cwiki.apache.org/qpid/faq.html">FAQ</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Documentation</H3><UL><LI><A href="http://qpid.apache.org/documentation.html#doc-release">Latest Release</A></LI><LI><A href="http://qpid.apache.org/documentation.html#doc-trunk">Trunk</A></LI><LI><A href="http://qpid.apache.org/documentation.html#doc-archives">Archive</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Community</H3><UL><LI><A href="http://qpid.apache.org/getting_involved.html">Getting Involved</A></LI><LI><A href="http://qpid.apache.org/source_repository.html">Source Repository</A></LI><LI><
A href="http://qpid.apache.org/mailing_lists.html">Mailing Lists</A></LI><LI><A href="https://cwiki.apache.org/qpid/">Wiki</A></LI><LI><A href="https://issues.apache.org/jira/browse/qpid">Issue Reporting</A></LI><LI><A href="http://qpid.apache.org/people.html">People</A></LI><LI><A href="http://qpid.apache.org/acknowledgements.html">Acknowledgements</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Developers</H3><UL><LI><A href="https://cwiki.apache.org/qpid/building.html">Building Qpid</A></LI><LI><A href="https://cwiki.apache.org/qpid/developer-pages.html">Developer Pages</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>About AMQP</H3><UL><LI><A href="http://qpid.apache.org/amqp.html">What is AMQP?</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>About Apache</H3><UL><LI><A href="
http://www.apache.org">Home</A></LI><LI><A href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</A></LI><LI><A href="http://www.apache.org/foundation/thanks.html">Thanks</A></LI><LI><A href="http://www.apache.org/security/">Security</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV></DIV><div class="main_text_area"><div class="main_text_area_top"></div><div class="main_text_area_body"><DIV class="breadcrumbs"><span class="breadcrumb-link"><a href="index.html">AMQP Messaging Broker (Java)</a></span> > <span class="breadcrumb-link"><a href="Java-Broker-High-Availability.html">High Availability</a></span> > <span class="breadcrumb-node">Migration of a non-HA store to HA</span></DIV><div class="section"><div class="titlepage"><div><div><h2 class="title"><a name="Java-Broker-High-Availability-MigrationFromNonHA"></a>13.14. 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 automat
ically 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/util/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 name="idp8378368"></a><p class="title"><b>Example 13.7. Enabling replication</b></p><div class="example-contents"><span class="command"><strong>
java -jar je-5.0.84.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.84 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 name="idp8369200"></a><p class="title"><b>Example 13.8. Example of XML configuration for HA message store</b></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 name="idp8382640"></a><p class="title"><b>Example 13.8. Example of XML configuration for HA message store</b></p><div class="example-contents"><pre class="programlisting">
<store>
<class>org.apache.qpid.server.store.berkeleydb.BDBHAMessageStore</class>
<environment-path>/path/to/store</environment-path>
Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-Monitoring-cluster.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-Monitoring-cluster.html?rev=1530450&r1=1530449&r2=1530450&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-Monitoring-cluster.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-Monitoring-cluster.html Tue Oct 8 22:32:49 2013
@@ -1,5 +1,5 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>13.9. Monitoring cluster</title><link rel="stylesheet" type="text/css" href="css/style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="AMQP Messaging Broker (Java)"><link rel="up" href="Java-Broker-High-Availability.html" title="Chapter 13. High Availability"><link rel="prev" href="Java-Broker-High-Availability-JMXAPI.html" title="13.8. Qpid JMX API for HA"><link rel="next" href="Java-Broker-High-Availability-DiskSpace.html" title="13.10. Disk space requirements"></head><body><div class="container" bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><DIV class="header"><DIV class="logo"><H1>Apache Qpidâ¢</H1><H2>Open Source AMQP Messaging</H2></DIV></DIV><DIV class="menu_box"><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Apache Qpid</H3><UL><LI><A href="http://qpid.apache.org/
index.html">Home</A></LI><LI><A href="http://qpid.apache.org/download.html">Download</A></LI><LI><A href="http://qpid.apache.org/getting_started.html">Getting Started</A></LI><LI><A href="http://www.apache.org/licenses/">License</A></LI><LI><A href="https://cwiki.apache.org/qpid/faq.html">FAQ</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Documentation</H3><UL><LI><A href="http://qpid.apache.org/documentation.html#doc-release">Latest Release</A></LI><LI><A href="http://qpid.apache.org/documentation.html#doc-trunk">Trunk</A></LI><LI><A href="http://qpid.apache.org/documentation.html#doc-archives">Archive</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Community</H3><UL><LI><A href="http://qpid.apache.org/getting_involved.html">Getting Involved</A></LI><LI><A href="http://qpid.apache.org/source_repository.html">Source Repository</A></LI><LI><A href
="http://qpid.apache.org/mailing_lists.html">Mailing Lists</A></LI><LI><A href="https://cwiki.apache.org/qpid/">Wiki</A></LI><LI><A href="https://issues.apache.org/jira/browse/qpid">Issue Reporting</A></LI><LI><A href="http://qpid.apache.org/people.html">People</A></LI><LI><A href="http://qpid.apache.org/acknowledgements.html">Acknowledgements</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Developers</H3><UL><LI><A href="https://cwiki.apache.org/qpid/building.html">Building Qpid</A></LI><LI><A href="https://cwiki.apache.org/qpid/developer-pages.html">Developer Pages</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>About AMQP</H3><UL><LI><A href="http://qpid.apache.org/amqp.html">What is AMQP?</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>About Apache</H3><UL><LI><A href="http:/
/www.apache.org">Home</A></LI><LI><A href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</A></LI><LI><A href="http://www.apache.org/foundation/thanks.html">Thanks</A></LI><LI><A href="http://www.apache.org/security/">Security</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV></DIV><div class="main_text_area"><div class="main_text_area_top"></div><div class="main_text_area_body"><DIV class="breadcrumbs"><span class="breadcrumb-link"><a href="index.html">AMQP Messaging Broker (Java)</a></span> > <span class="breadcrumb-link"><a href="Java-Broker-High-Availability.html">High Availability</a></span> > <span class="breadcrumb-node">Monitoring cluster</span></DIV><div class="section"><div class="titlepage"><div><div><h2 class="title"><a name="Java-Broker-High-Availability-Monitoring-cluster"></a>13.9. 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 name="idp8324048"></a><p
class="title"><b>Example 13.4. Using <code class="classname">DbPing</code> utility for monitoring HA nodes.</b></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 name="idp8337488"></a><p
class="title"><b>Example 13.4. Using <code class="classname">DbPing</code> utility for monitoring HA nodes.</b></p><div class="example-contents"><span class="command"><strong>
java -jar je-5.0.84.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/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-OfferingsOfJavaBroker.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-OfferingsOfJavaBroker.html?rev=1530450&r1=1530449&r2=1530450&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-OfferingsOfJavaBroker.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-OfferingsOfJavaBroker.html Tue Oct 8 22:32:49 2013
@@ -7,7 +7,7 @@
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 href="#ftn.idp8121200" class="footnote" name="idp8121200"><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 href="#ftn.idp8134640" class="footnote" name="idp8134640"><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 width="100" align="left"><div id="ftn.idp8121200" class="footnote"><p><a href="#idp8121200" class="para"><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 width="100" align="left"><div id="ftn.idp8134640" class="footnote"><p><a href="#idp8134640" class="para"><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><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Java-Broker-High-Availability.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="Java-Broker-High-Availability.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="Java-Broker-High-Availability-TwoNodeCluster.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 13. High Availability </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 13.3. Two Node Cluster</td></tr></table></div><div class="main_text_area_bottom"></div></div></div></body></html>
Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-Performance.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-Performance.html?rev=1530450&r1=1530449&r2=1530450&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-Performance.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-Performance.html Tue Oct 8 22:32:49 2013
@@ -102,6 +102,6 @@
<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 name="idp8446128"></a><p class="title"><b>Figure 13.8. Test results</b></p><div class="figure-contents"><div><img src="images/HA-perftests-results.png" alt="Test results"></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_Coa
lescingSync" title="13.6.2. 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 name="idp8459568"></a><p class="title"><b>Figure 13.8. Test results</b></p><div class="figure-contents"><div><img src="images/HA-perftests-results.png" alt="Test results"></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_Coa
lescingSync" title="13.6.2. 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><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Java-Broker-High-Availability-DisasterRecovery.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="Java-Broker-High-Availability.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="Java-Broker-Virtual-Hosts-Configuration-File.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">13.15. Disaster Recovery </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 14. Virtual Host XML configuration file</td></tr></table></div><div class="main_text_area_bottom"></div></div></d
iv></body></html>
Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-TwoNodeCluster.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-TwoNodeCluster.html?rev=1530450&r1=1530449&r2=1530450&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-TwoNodeCluster.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-TwoNodeCluster.html Tue Oct 8 22:32:49 2013
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>13.3. Two Node Cluster</title><link rel="stylesheet" type="text/css" href="css/style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="AMQP Messaging Broker (Java)"><link rel="up" href="Java-Broker-High-Availability.html" title="Chapter 13. High Availability"><link rel="prev" href="Java-Broker-High-Availability-OfferingsOfJavaBroker.html" title="13.2. HA offerings of the Java Broker"><link rel="next" href="Java-Broker-High-Availability-MultiNodeCluster.html" title="13.4. Multi Node Cluster"></head><body><div class="container" bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><DIV class="header"><DIV class="logo"><H1>Apache Qpidâ¢</H1><H2>Open Source AMQP Messaging</H2></DIV></DIV><DIV class="menu_box"><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Apache Qpid</H3><UL><LI><A hre
f="http://qpid.apache.org/index.html">Home</A></LI><LI><A href="http://qpid.apache.org/download.html">Download</A></LI><LI><A href="http://qpid.apache.org/getting_started.html">Getting Started</A></LI><LI><A href="http://www.apache.org/licenses/">License</A></LI><LI><A href="https://cwiki.apache.org/qpid/faq.html">FAQ</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Documentation</H3><UL><LI><A href="http://qpid.apache.org/documentation.html#doc-release">Latest Release</A></LI><LI><A href="http://qpid.apache.org/documentation.html#doc-trunk">Trunk</A></LI><LI><A href="http://qpid.apache.org/documentation.html#doc-archives">Archive</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Community</H3><UL><LI><A href="http://qpid.apache.org/getting_involved.html">Getting Involved</A></LI><LI><A href="http://qpid.apache.org/source_repository.html">Source Repo
sitory</A></LI><LI><A href="http://qpid.apache.org/mailing_lists.html">Mailing Lists</A></LI><LI><A href="https://cwiki.apache.org/qpid/">Wiki</A></LI><LI><A href="https://issues.apache.org/jira/browse/qpid">Issue Reporting</A></LI><LI><A href="http://qpid.apache.org/people.html">People</A></LI><LI><A href="http://qpid.apache.org/acknowledgements.html">Acknowledgements</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Developers</H3><UL><LI><A href="https://cwiki.apache.org/qpid/building.html">Building Qpid</A></LI><LI><A href="https://cwiki.apache.org/qpid/developer-pages.html">Developer Pages</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>About AMQP</H3><UL><LI><A href="http://qpid.apache.org/amqp.html">What is AMQP?</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>About Apache</
H3><UL><LI><A href="http://www.apache.org">Home</A></LI><LI><A href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</A></LI><LI><A href="http://www.apache.org/foundation/thanks.html">Thanks</A></LI><LI><A href="http://www.apache.org/security/">Security</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV></DIV><div class="main_text_area"><div class="main_text_area_top"></div><div class="main_text_area_body"><DIV class="breadcrumbs"><span class="breadcrumb-link"><a href="index.html">AMQP Messaging Broker (Java)</a></span> > <span class="breadcrumb-link"><a href="Java-Broker-High-Availability.html">High Availability</a></span> > <span class="breadcrumb-node">Two Node Cluster</span></DIV><div class="section"><div class="titlepage"><div><div><h2 class="title"><a name="Java-Broker-High-Availability-TwoNodeCluster"></a>13.3. Two Node Cluster</h2></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp8125824"></a>13.3
.1. Overview</h3></div></div></div><p>In this HA solution, a cluster is formed with two nodes. one node serves as
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>13.3. Two Node Cluster</title><link rel="stylesheet" type="text/css" href="css/style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="AMQP Messaging Broker (Java)"><link rel="up" href="Java-Broker-High-Availability.html" title="Chapter 13. High Availability"><link rel="prev" href="Java-Broker-High-Availability-OfferingsOfJavaBroker.html" title="13.2. HA offerings of the Java Broker"><link rel="next" href="Java-Broker-High-Availability-MultiNodeCluster.html" title="13.4. Multi Node Cluster"></head><body><div class="container" bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><DIV class="header"><DIV class="logo"><H1>Apache Qpidâ¢</H1><H2>Open Source AMQP Messaging</H2></DIV></DIV><DIV class="menu_box"><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Apache Qpid</H3><UL><LI><A hre
f="http://qpid.apache.org/index.html">Home</A></LI><LI><A href="http://qpid.apache.org/download.html">Download</A></LI><LI><A href="http://qpid.apache.org/getting_started.html">Getting Started</A></LI><LI><A href="http://www.apache.org/licenses/">License</A></LI><LI><A href="https://cwiki.apache.org/qpid/faq.html">FAQ</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Documentation</H3><UL><LI><A href="http://qpid.apache.org/documentation.html#doc-release">Latest Release</A></LI><LI><A href="http://qpid.apache.org/documentation.html#doc-trunk">Trunk</A></LI><LI><A href="http://qpid.apache.org/documentation.html#doc-archives">Archive</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Community</H3><UL><LI><A href="http://qpid.apache.org/getting_involved.html">Getting Involved</A></LI><LI><A href="http://qpid.apache.org/source_repository.html">Source Repo
sitory</A></LI><LI><A href="http://qpid.apache.org/mailing_lists.html">Mailing Lists</A></LI><LI><A href="https://cwiki.apache.org/qpid/">Wiki</A></LI><LI><A href="https://issues.apache.org/jira/browse/qpid">Issue Reporting</A></LI><LI><A href="http://qpid.apache.org/people.html">People</A></LI><LI><A href="http://qpid.apache.org/acknowledgements.html">Acknowledgements</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Developers</H3><UL><LI><A href="https://cwiki.apache.org/qpid/building.html">Building Qpid</A></LI><LI><A href="https://cwiki.apache.org/qpid/developer-pages.html">Developer Pages</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>About AMQP</H3><UL><LI><A href="http://qpid.apache.org/amqp.html">What is AMQP?</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>About Apache</
H3><UL><LI><A href="http://www.apache.org">Home</A></LI><LI><A href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</A></LI><LI><A href="http://www.apache.org/foundation/thanks.html">Thanks</A></LI><LI><A href="http://www.apache.org/security/">Security</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV></DIV><div class="main_text_area"><div class="main_text_area_top"></div><div class="main_text_area_body"><DIV class="breadcrumbs"><span class="breadcrumb-link"><a href="index.html">AMQP Messaging Broker (Java)</a></span> > <span class="breadcrumb-link"><a href="Java-Broker-High-Availability.html">High Availability</a></span> > <span class="breadcrumb-node">Two Node Cluster</span></DIV><div class="section"><div class="titlepage"><div><div><h2 class="title"><a name="Java-Broker-High-Availability-TwoNodeCluster"></a>13.3. Two Node Cluster</h2></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp8139264"></a>13.3
.1. Overview</h3></div></div></div><p>In this HA solution, a cluster is formed with two nodes. one node serves as
<span class="bold"><strong>master</strong></span> and the other is a <span class="bold"><strong>replica</strong></span>.
</p><p>All data and state required for the operation of the virtual host is automatically sent from the
master to the replica. This is called the replication stream. The master virtual host confirms each
@@ -16,11 +16,11 @@
is described in more detail later.
</p><p>Clients connect to the cluster using a <a class="link" href="Java-Broker-High-Availability-ClientFailover.html" title="13.7. Client failover configuration">failover url</a>.
This allows the client to maintain a connection to the master in a way that is transparent
- to the client application.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp8133392"></a>13.3.2. Depictions of cluster operation</h3></div></div></div><p>In this section, the operation of the cluster is depicted through a series of figures
- supported by explanatory text.</p><div class="figure"><a name="idp8134864"></a><p class="title"><b>Figure 13.1. Key for figures</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/HA-2N-Key.png" alt="Key to figures"></div></div></div><br class="figure-break"><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="Java-Broker-High-Availability-TwoNodeNormalOperation"></a>13.3.2.1. Normal Operation</h4></div></div></div><p>The figure below illustrates normal operation. Clients connecting to the cluster by way
+ to the client application.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp8146832"></a>13.3.2. Depictions of cluster operation</h3></div></div></div><p>In this section, the operation of the cluster is depicted through a series of figures
+ supported by explanatory text.</p><div class="figure"><a name="idp8148304"></a><p class="title"><b>Figure 13.1. Key for figures</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/HA-2N-Key.png" alt="Key to figures"></div></div></div><br class="figure-break"><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="Java-Broker-High-Availability-TwoNodeNormalOperation"></a>13.3.2.1. Normal Operation</h4></div></div></div><p>The figure below illustrates normal operation. Clients connecting to the cluster by way
of the failover URL achieve a connection to the master. As clients perform work (message
production, consumption, queue creation etc), the master additionally sends this data to the
- replica over the network.</p><div class="figure"><a name="idp8140320"></a><p class="title"><b>Figure 13.2. Normal operation of a two-node cluster</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/HA-2N-Normal.png" alt="Normal operation"></div></div></div><br class="figure-break"></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="Java-Broker-High-Availability-TwoNodeMasterFailure"></a>13.3.2.2. Master Failure and Recovery</h4></div></div></div><p>The figure below illustrates a sequence of events whereby the master suffers a failure
+ replica over the network.</p><div class="figure"><a name="idp8153760"></a><p class="title"><b>Figure 13.2. Normal operation of a two-node cluster</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/HA-2N-Normal.png" alt="Normal operation"></div></div></div><br class="figure-break"></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="Java-Broker-High-Availability-TwoNodeMasterFailure"></a>13.3.2.2. Master Failure and Recovery</h4></div></div></div><p>The figure below illustrates a sequence of events whereby the master suffers a failure
and the replica is made the master to allow the clients to continue to work. Later the
old master is repaired and comes back on-line in replica role.</p><p>The item numbers in this list apply to the numbered boxes in the figure below.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>System operating normally</p></li><li class="listitem"><p>Master suffers a failure and disconnects all clients. Replica realises that it is no
longer in contact with master. Clients begin to try to reconnect to the cluster, although these
@@ -29,7 +29,7 @@
to designate the replica as primary, allowing it to assume the role of master despite the other node being down.
This primary designation is performed using <a class="link" href="Java-Broker-High-Availability-JMXAPI.html" title="13.8. Qpid JMX API for HA">JMX</a>.</p></li><li class="listitem"><p>Client connections to the new master succeed and the <span class="bold"><strong>service is restored
</strong></span>, albeit without a replica.</p></li><li class="listitem"><p>The old master is repaired and brought back on-line. It automatically rejoins the cluster
- in the <span class="bold"><strong>replica</strong></span> role.</p></li></ol></div><div class="figure"><a name="idp8154272"></a><p class="title"><b>Figure 13.3. Failure of master and recovery sequence</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/HA-2N-MasterFail.png" alt="Failure of master and subsequent recovery sequence"></div></div></div><br class="figure-break"></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="Java-Broker-High-Availability-TwoNodeReplicaFailure"></a>13.3.2.3. Replica Failure and Recovery</h4></div></div></div><p>The figure that follows illustrates a sequence of events whereby the replica suffers a failure
+ in the <span class="bold"><strong>replica</strong></span> role.</p></li></ol></div><div class="figure"><a name="idp8167712"></a><p class="title"><b>Figure 13.3. Failure of master and recovery sequence</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/HA-2N-MasterFail.png" alt="Failure of master and subsequent recovery sequence"></div></div></div><br class="figure-break"></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="Java-Broker-High-Availability-TwoNodeReplicaFailure"></a>13.3.2.3. Replica Failure and Recovery</h4></div></div></div><p>The figure that follows illustrates a sequence of events whereby the replica suffers a failure
leaving the master to continue processing alone. Later the replica is repaired and is restarted.
It rejoins the cluster so that it is once again ready to take over in the event of master failure.</p><p>The behavior of the replica failure case is governed by the <code class="varname">designatedPrimary</code>
configuration item. If set true on the master, the master will continue to operate solo without outside
@@ -38,14 +38,14 @@
that <code class="varname">designatedPrimary</code> is true on the original master node.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>System operating normally</p></li><li class="listitem"><p>Replica suffers a failure. Master realises that replica longer in contact but as
<code class="varname">designatedPrimary</code> is true, master continues processing solo and thus client
connections are uninterrupted by the loss of the replica. System continues operating normally, albeit
- with a single node.</p></li><li class="listitem"><p>Replica is repaired.</p></li><li class="listitem"><p>After catching up with missed work, replica is once again ready to take over in the event of master failure.</p></li></ol></div><div class="figure"><a name="idp8166640"></a><p class="title"><b>Figure 13.4. Failure of replica and subsequent recovery sequence</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/HA-2N-ReplicaFail.png" alt="Failure of replica and subsequent recovery sequence"></div></div></div><br class="figure-break"></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="Java-Broker-High-Availability-TwoNodeNetworkPartition"></a>13.3.2.4. Network Partition and Recovery</h4></div></div></div><p>The figure below illustrates the sequence of events that would occur if the network between
+ with a single node.</p></li><li class="listitem"><p>Replica is repaired.</p></li><li class="listitem"><p>After catching up with missed work, replica is once again ready to take over in the event of master failure.</p></li></ol></div><div class="figure"><a name="idp8180080"></a><p class="title"><b>Figure 13.4. Failure of replica and subsequent recovery sequence</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/HA-2N-ReplicaFail.png" alt="Failure of replica and subsequent recovery sequence"></div></div></div><br class="figure-break"></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="Java-Broker-High-Availability-TwoNodeNetworkPartition"></a>13.3.2.4. Network Partition and Recovery</h4></div></div></div><p>The figure below illustrates the sequence of events that would occur if the network between
master and replica were to suffer a partition, and the nodes were out of contact with one and other.</p><p>As with <a class="link" href="Java-Broker-High-Availability-TwoNodeCluster.html#Java-Broker-High-Availability-TwoNodeReplicaFailure" title="13.3.2.3. Replica Failure and Recovery">Replica Failure and Recovery</a>, the
behaviour is governed by the <code class="varname">designatedPrimary</code>.
Only if <code class="varname">designatedPrimary</code> is true on the master, will the master continue solo.</p><p>The item numbers in this list apply to the numbered boxes in the figure below. This example assumes
that <code class="varname">designatedPrimary</code> is true on the original master node.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>System operating normally</p></li><li class="listitem"><p>Network suffers a failure. Master realises that replica longer in contact but as
<code class="varname">designatedPrimary</code> is true, master continues processing solo and thus client
connections are uninterrupted by the network partition between master and replica.</p></li><li class="listitem"><p>Network is repaired.</p></li><li class="listitem"><p>After catching up with missed work, replica is once again ready to take over in the event of master failure.
- System operating normally again.</p></li></ol></div><div class="figure"><a name="idp8179856"></a><p class="title"><b>Figure 13.5. Partition of the network separating master and replica</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/HA-2N-NetworkPartition.png" alt="Network Partition and Recovery"></div></div></div><br class="figure-break"></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="Java-Broker-High-Availability-TwoNodeSplitBrain"></a>13.3.2.5. Split Brain</h4></div></div></div><p>A <a class="ulink" href="http://en.wikipedia.org/wiki/Split-brain_(computing)" target="_top">split-brain</a>
+ System operating normally again.</p></li></ol></div><div class="figure"><a name="idp8193296"></a><p class="title"><b>Figure 13.5. Partition of the network separating master and replica</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/HA-2N-NetworkPartition.png" alt="Network Partition and Recovery"></div></div></div><br class="figure-break"></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="Java-Broker-High-Availability-TwoNodeSplitBrain"></a>13.3.2.5. Split Brain</h4></div></div></div><p>A <a class="ulink" href="http://en.wikipedia.org/wiki/Split-brain_(computing)" target="_top">split-brain</a>
is a situation where the two node cluster has two masters. BDB normally strives to prevent
this situation arising by preventing two nodes in a cluster being master at the same time.
However, if the network suffers a partition, and the third-party intervenes incorrectly
@@ -56,4 +56,4 @@
<code class="varname">designatedPrimary</code> is true, master continues processing solo. Client
connections are uninterrupted by the network partition.</p><p>A third-party <span class="bold"><strong>erroneously</strong></span> designates the replica as primary while the
original master continues running (now solo).</p></li><li class="listitem"><p>As the nodes cannot see one and other, both behave as masters. Clients may perform work against
- both master nodes.</p></li></ol></div><div class="figure"><a name="idp8193376"></a><p class="title"><b>Figure 13.6. Split Brain</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/HA-2N-SplitBrain.png" alt="Split Brain"></div></div></div><br class="figure-break"></div></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Java-Broker-High-Availability-OfferingsOfJavaBroker.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="Java-Broker-High-Availability.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="Java-Broker-High-Availability-MultiNodeCluster.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">13.2. HA offerings of the Java Broker </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 13.4. Multi
Node Cluster</td></tr></table></div><div class="main_text_area_bottom"></div></div></div></body></html>
+ both master nodes.</p></li></ol></div><div class="figure"><a name="idp8206816"></a><p class="title"><b>Figure 13.6. Split Brain</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/HA-2N-SplitBrain.png" alt="Split Brain"></div></div></div><br class="figure-break"></div></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Java-Broker-High-Availability-OfferingsOfJavaBroker.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="Java-Broker-High-Availability.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="Java-Broker-High-Availability-MultiNodeCluster.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">13.2. HA offerings of the Java Broker </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 13.4. Multi
Node Cluster</td></tr></table></div><div class="main_text_area_bottom"></div></div></div></body></html>
Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability.html?rev=1530450&r1=1530449&r2=1530450&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability.html Tue Oct 8 22:32:49 2013
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Chapter 13. High Availability</title><link rel="stylesheet" type="text/css" href="css/style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="AMQP Messaging Broker (Java)"><link rel="up" href="index.html" title="AMQP Messaging Broker (Java)"><link rel="prev" href="Java-Broker-Close-Connection-When-No-Route.html" title="12.6. Closing client connections on unroutable mandatory messages"><link rel="next" href="Java-Broker-High-Availability-OfferingsOfJavaBroker.html" title="13.2. HA offerings of the Java Broker"></head><body><div class="container" bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><DIV class="header"><DIV class="logo"><H1>Apache Qpidâ¢</H1><H2>Open Source AMQP Messaging</H2></DIV></DIV><DIV class="menu_box"><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Apache Qpid</H
3><UL><LI><A href="http://qpid.apache.org/index.html">Home</A></LI><LI><A href="http://qpid.apache.org/download.html">Download</A></LI><LI><A href="http://qpid.apache.org/getting_started.html">Getting Started</A></LI><LI><A href="http://www.apache.org/licenses/">License</A></LI><LI><A href="https://cwiki.apache.org/qpid/faq.html">FAQ</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Documentation</H3><UL><LI><A href="http://qpid.apache.org/documentation.html#doc-release">Latest Release</A></LI><LI><A href="http://qpid.apache.org/documentation.html#doc-trunk">Trunk</A></LI><LI><A href="http://qpid.apache.org/documentation.html#doc-archives">Archive</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Community</H3><UL><LI><A href="http://qpid.apache.org/getting_involved.html">Getting Involved</A></LI><LI><A href="http://qpid.apache.org/source_repository.h
tml">Source Repository</A></LI><LI><A href="http://qpid.apache.org/mailing_lists.html">Mailing Lists</A></LI><LI><A href="https://cwiki.apache.org/qpid/">Wiki</A></LI><LI><A href="https://issues.apache.org/jira/browse/qpid">Issue Reporting</A></LI><LI><A href="http://qpid.apache.org/people.html">People</A></LI><LI><A href="http://qpid.apache.org/acknowledgements.html">Acknowledgements</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Developers</H3><UL><LI><A href="https://cwiki.apache.org/qpid/building.html">Building Qpid</A></LI><LI><A href="https://cwiki.apache.org/qpid/developer-pages.html">Developer Pages</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>About AMQP</H3><UL><LI><A href="http://qpid.apache.org/amqp.html">What is AMQP?</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H
3>About Apache</H3><UL><LI><A href="http://www.apache.org">Home</A></LI><LI><A href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</A></LI><LI><A href="http://www.apache.org/foundation/thanks.html">Thanks</A></LI><LI><A href="http://www.apache.org/security/">Security</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV></DIV><div class="main_text_area"><div class="main_text_area_top"></div><div class="main_text_area_body"><DIV class="breadcrumbs"><span class="breadcrumb-link"><a href="index.html">AMQP Messaging Broker (Java)</a></span> > <span class="breadcrumb-node">High Availability</span></DIV><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="Java-Broker-High-Availability"></a>Chapter 13. High Availability</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="Java-Broker-High-Availability.html#Java-Broker-High-Availability-GeneralIntroduction">13.1. General
Introduction</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-OfferingsOfJavaBroker.html">13.2. HA offerings of the Java Broker</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-TwoNodeCluster.html">13.3. Two Node Cluster</a></span></dt><dd><dl><dt><span class="section"><a href="Java-Broker-High-Availability-TwoNodeCluster.html#idp8125824">13.3.1. Overview</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-TwoNodeCluster.html#idp8133392">13.3.2. Depictions of cluster operation</a></span></dt></dl></dd><dt><span class="section"><a href="Java-Broker-High-Availability-MultiNodeCluster.html">13.4. Multi Node Cluster</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-Configuration.html">13.5. Configuring a Virtual Host to be a node</a></span></dt><dd><dl><dt><span class="section"><a href="Java-Broker-High-Availability-Configuration.html#Java-Broker-High-Availability-Con
figuration_BDBEnvVars">13.5.1. Passing BDB environment and replication configuration options</a></span></dt></dl></dd><dt><span class="section"><a href="Java-Broker-High-Availability-DurabilityGuarantee.html">13.6. Durability Guarantees</a></span></dt><dd><dl><dt><span class="section"><a href="Java-Broker-High-Availability-DurabilityGuarantee.html#Java-Broker-High-Availability-DurabilityGuarantee_BDBControls">13.6.1. BDB Durability Controls</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-DurabilityGuarantee.html#Java-Broker-High-Availability-DurabilityGuarantee_CoalescingSync">13.6.2. Coalescing-sync</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-DurabilityGuarantee.html#Java-Broker-High-Availability-DurabilityGuarantee_Default">13.6.3. Default</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-DurabilityGuarantee.html#Java-Broker-High-Availability-DurabilityGuarantee_Examples">13.6.4. Exam
ples</a></span></dt></dl></dd><dt><span class="section"><a href="Java-Broker-High-Availability-ClientFailover.html">13.7. Client failover configuration</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-JMXAPI.html">13.8. Qpid JMX API for HA</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-Monitoring-cluster.html">13.9. Monitoring cluster</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-DiskSpace.html">13.10. Disk space requirements</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-Network-Requirements.html">13.11. Network Requirements</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-Security.html">13.12. Security</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-Backup.html">13.13. Backups</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-MigrationFromNonHA.html">13.14. Mig
ration of a non-HA store to HA</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-DisasterRecovery.html">13.15. Disaster Recovery</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-Performance.html">13.16. Performance</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title"><a name="Java-Broker-High-Availability-GeneralIntroduction"></a>13.1. General Introduction</h2></div></div></div><p>The term High Availability (HA) usually refers to having a number of instances of a service such as a Message Broker
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Chapter 13. High Availability</title><link rel="stylesheet" type="text/css" href="css/style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="AMQP Messaging Broker (Java)"><link rel="up" href="index.html" title="AMQP Messaging Broker (Java)"><link rel="prev" href="Java-Broker-Close-Connection-When-No-Route.html" title="12.6. Closing client connections on unroutable mandatory messages"><link rel="next" href="Java-Broker-High-Availability-OfferingsOfJavaBroker.html" title="13.2. HA offerings of the Java Broker"></head><body><div class="container" bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><DIV class="header"><DIV class="logo"><H1>Apache Qpidâ¢</H1><H2>Open Source AMQP Messaging</H2></DIV></DIV><DIV class="menu_box"><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Apache Qpid</H
3><UL><LI><A href="http://qpid.apache.org/index.html">Home</A></LI><LI><A href="http://qpid.apache.org/download.html">Download</A></LI><LI><A href="http://qpid.apache.org/getting_started.html">Getting Started</A></LI><LI><A href="http://www.apache.org/licenses/">License</A></LI><LI><A href="https://cwiki.apache.org/qpid/faq.html">FAQ</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Documentation</H3><UL><LI><A href="http://qpid.apache.org/documentation.html#doc-release">Latest Release</A></LI><LI><A href="http://qpid.apache.org/documentation.html#doc-trunk">Trunk</A></LI><LI><A href="http://qpid.apache.org/documentation.html#doc-archives">Archive</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Community</H3><UL><LI><A href="http://qpid.apache.org/getting_involved.html">Getting Involved</A></LI><LI><A href="http://qpid.apache.org/source_repository.h
tml">Source Repository</A></LI><LI><A href="http://qpid.apache.org/mailing_lists.html">Mailing Lists</A></LI><LI><A href="https://cwiki.apache.org/qpid/">Wiki</A></LI><LI><A href="https://issues.apache.org/jira/browse/qpid">Issue Reporting</A></LI><LI><A href="http://qpid.apache.org/people.html">People</A></LI><LI><A href="http://qpid.apache.org/acknowledgements.html">Acknowledgements</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Developers</H3><UL><LI><A href="https://cwiki.apache.org/qpid/building.html">Building Qpid</A></LI><LI><A href="https://cwiki.apache.org/qpid/developer-pages.html">Developer Pages</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>About AMQP</H3><UL><LI><A href="http://qpid.apache.org/amqp.html">What is AMQP?</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H
3>About Apache</H3><UL><LI><A href="http://www.apache.org">Home</A></LI><LI><A href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</A></LI><LI><A href="http://www.apache.org/foundation/thanks.html">Thanks</A></LI><LI><A href="http://www.apache.org/security/">Security</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV></DIV><div class="main_text_area"><div class="main_text_area_top"></div><div class="main_text_area_body"><DIV class="breadcrumbs"><span class="breadcrumb-link"><a href="index.html">AMQP Messaging Broker (Java)</a></span> > <span class="breadcrumb-node">High Availability</span></DIV><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="Java-Broker-High-Availability"></a>Chapter 13. High Availability</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="Java-Broker-High-Availability.html#Java-Broker-High-Availability-GeneralIntroduction">13.1. General
Introduction</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-OfferingsOfJavaBroker.html">13.2. HA offerings of the Java Broker</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-TwoNodeCluster.html">13.3. Two Node Cluster</a></span></dt><dd><dl><dt><span class="section"><a href="Java-Broker-High-Availability-TwoNodeCluster.html#idp8139264">13.3.1. Overview</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-TwoNodeCluster.html#idp8146832">13.3.2. Depictions of cluster operation</a></span></dt></dl></dd><dt><span class="section"><a href="Java-Broker-High-Availability-MultiNodeCluster.html">13.4. Multi Node Cluster</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-Configuration.html">13.5. Configuring a Virtual Host to be a node</a></span></dt><dd><dl><dt><span class="section"><a href="Java-Broker-High-Availability-Configuration.html#Java-Broker-High-Availability-Con
figuration_BDBEnvVars">13.5.1. Passing BDB environment and replication configuration options</a></span></dt></dl></dd><dt><span class="section"><a href="Java-Broker-High-Availability-DurabilityGuarantee.html">13.6. Durability Guarantees</a></span></dt><dd><dl><dt><span class="section"><a href="Java-Broker-High-Availability-DurabilityGuarantee.html#Java-Broker-High-Availability-DurabilityGuarantee_BDBControls">13.6.1. BDB Durability Controls</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-DurabilityGuarantee.html#Java-Broker-High-Availability-DurabilityGuarantee_CoalescingSync">13.6.2. Coalescing-sync</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-DurabilityGuarantee.html#Java-Broker-High-Availability-DurabilityGuarantee_Default">13.6.3. Default</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-DurabilityGuarantee.html#Java-Broker-High-Availability-DurabilityGuarantee_Examples">13.6.4. Exam
ples</a></span></dt></dl></dd><dt><span class="section"><a href="Java-Broker-High-Availability-ClientFailover.html">13.7. Client failover configuration</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-JMXAPI.html">13.8. Qpid JMX API for HA</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-Monitoring-cluster.html">13.9. Monitoring cluster</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-DiskSpace.html">13.10. Disk space requirements</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-Network-Requirements.html">13.11. Network Requirements</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-Security.html">13.12. Security</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-Backup.html">13.13. Backups</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-MigrationFromNonHA.html">13.14. Mig
ration of a non-HA store to HA</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-DisasterRecovery.html">13.15. Disaster Recovery</a></span></dt><dt><span class="section"><a href="Java-Broker-High-Availability-Performance.html">13.16. Performance</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title"><a name="Java-Broker-High-Availability-GeneralIntroduction"></a>13.1. General Introduction</h2></div></div></div><p>The term High Availability (HA) usually refers to having a number of instances of a service such as a Message Broker
available so that should a service unexpectedly fail, or requires to be shutdown for maintenance, users may quickly connect
to another instance and continue their work with minimal interuption. HA is one way to make a overall system more resilient
by eliminating a single point of failure from a system.</p><p>HA offerings are usually categorised as <span class="bold"><strong>Active/Active</strong></span> or <span class="bold"><strong>Active/Passive</strong></span>.
Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Queues.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Queues.html?rev=1530450&r1=1530449&r2=1530450&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Queues.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Queues.html Tue Oct 8 22:32:49 2013
@@ -36,11 +36,11 @@
The maximum number of delivery retries before message is sent to the DLQ can be specified in "Maximum Delivery Retries" field.
However, configuring of maximum delivery retries on a queue without DLQ(AlternateExchange) will result in messages
being discarded after the limit is reached.</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="Java-Broker-Queues-OtherTypes-CreateUsingJmsOrJmx"></a>9.1.5.2. Using JMX or AMQP</h4></div></div></div><p>To create a priority, sorted or LVQ queue programmatically from JMX or using a Qpid
- extension to JMS, pass the appropriate queue-declare arguments.</p><div class="table"><a name="idp7141408"></a><p class="title"><b>Table 9.1. Queue-declare arguments understood for priority, sorted and LVQ queues</b></p><div class="table-contents"><table summary="Queue-declare arguments understood for priority, sorted and LVQ queues" border="1"><colgroup><col><col><col><col></colgroup><thead><tr><th>Queue type</th><th>Argument name</th><th>Argument name</th><th>Argument Description</th></tr></thead><tbody><tr><td>priority</td><td>x-qpid-priorities</td><td>java.lang.Integer</td><td>Specifies a priority queue with given number priorities</td></tr><tr><td>sorted</td><td>qpid.queue_sort_key</td><td>java.lang.String</td><td>Specifies sorted queue with given message property used to sort the
+ extension to JMS, pass the appropriate queue-declare arguments.</p><div class="table"><a name="idp7151312"></a><p class="title"><b>Table 9.1. Queue-declare arguments understood for priority, sorted and LVQ queues</b></p><div class="table-contents"><table summary="Queue-declare arguments understood for priority, sorted and LVQ queues" border="1"><colgroup><col><col><col><col></colgroup><thead><tr><th>Queue type</th><th>Argument name</th><th>Argument name</th><th>Argument Description</th></tr></thead><tbody><tr><td>priority</td><td>x-qpid-priorities</td><td>java.lang.Integer</td><td>Specifies a priority queue with given number priorities</td></tr><tr><td>sorted</td><td>qpid.queue_sort_key</td><td>java.lang.String</td><td>Specifies sorted queue with given message property used to sort the
entries</td></tr><tr><td>lvq</td><td>qpid.last_value_queue_key</td><td>java.lang.String</td><td>Specifies lvq queue with given message property used to conflate the
entries</td></tr></tbody></table></div></div><br class="table-break"><p>The following example illustrates the creation of the a LVQ queue from a
javax.jms.Session object. Note that this utilises a Qpid specific extension to JMS and
- involves casting the session object back to its Qpid base-class.</p><div class="example"><a name="idp7152208"></a><p class="title"><b>Example 9.1. Creation of an LVQ using the Qpid extension to JMS</b></p><div class="example-contents"><pre class="programlisting">Map<String,Object> arguments = new HashMap<String, Object>();
+ involves casting the session object back to its Qpid base-class.</p><div class="example"><a name="idp7162112"></a><p class="title"><b>Example 9.1. Creation of an LVQ using the Qpid extension to JMS</b></p><div class="example-contents"><pre class="programlisting">Map<String,Object> arguments = new HashMap<String, Object>();
arguments.put("qpid.last_value_queue_key","ISIN");
AMQDestination amqQueue = (AMQDestination) context.lookup("myqueue");
((AMQSession<?,?>) session).createQueue(
@@ -50,7 +50,7 @@ AMQDestination amqQueue = (AMQDestinatio
amqQueue.isExclusive(),
arguments);
</pre></div></div><br class="example-break"><p> The following example illustrates the creation of the sorted queue from a the JMX
- interface using the ManagedBroker interface. </p><div class="example"><a name="idp7154352"></a><p class="title"><b>Example 9.2. Creation of a sorted queue using JMX</b></p><div class="example-contents"><pre class="programlisting">Map<String, Object> environment = new HashMap<String, Object>();
+ interface using the ManagedBroker interface. </p><div class="example"><a name="idp7164256"></a><p class="title"><b>Example 9.2. Creation of a sorted queue using JMX</b></p><div class="example-contents"><pre class="programlisting">Map<String, Object> environment = new HashMap<String, Object>();
environment.put(JMXConnector.CREDENTIALS, new String[] {"admin","password"});
// Connect to service
JMXServiceURL url = new JMXServiceURL("service:jmx:rmi:///jndi/rmi://localhost:8999/jmxrmi");
@@ -69,7 +69,7 @@ managedBroker.createNewQueue("myqueue",
an extension to JMS), using JMX API, using REST interfaces or Web Management Console.</p><p>A queue can be bound to different exchanges at the same time.
Also, a queue can be bound to the same exchange multiple times.
Differenent binding keys can be used to bind a queue to the same topic or direct exchanges.</p><p>Binding attributes can be specified on binding creation to allow filtering of messages accepted by the queue using a selector expression
- or/and specifying whether messages published by its own connection should be delivered to it.</p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="Java-Broker-Queues-OtherTypes-BindingUsingManagement"></a>9.1.6.1. Using Web Management Console</h4></div></div></div><p>A queue can be bound to an exchange by clicking on "Add Binding" button on a Queue tab or an Exchange tab.</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="Java-Broker-Queues-OtherTypes-BindingUsingJmsOrJmx"></a>9.1.6.2. Using JMX or AMQP</h4></div></div></div><p>The following example illustrates the creation of queue binding to topic exchange with JMS client.</p><div class="example"><a name="idp7165424"></a><p class="title"><b>Example 9.3. Binding a queue using JMS</b></p><div class="example-contents"><pre class="programlisting">ConnectionFactory connectionFactory = ...
+ or/and specifying whether messages published by its own connection should be delivered to it.</p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="Java-Broker-Queues-OtherTypes-BindingUsingManagement"></a>9.1.6.1. Using Web Management Console</h4></div></div></div><p>A queue can be bound to an exchange by clicking on "Add Binding" button on a Queue tab or an Exchange tab.</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="Java-Broker-Queues-OtherTypes-BindingUsingJmsOrJmx"></a>9.1.6.2. Using JMX or AMQP</h4></div></div></div><p>The following example illustrates the creation of queue binding to topic exchange with JMS client.</p><div class="example"><a name="idp7175328"></a><p class="title"><b>Example 9.3. Binding a queue using JMS</b></p><div class="example-contents"><pre class="programlisting">ConnectionFactory connectionFactory = ...
Connection connection = connectionFactory.createConnection();
AMQSession<?, ?> session = (AMQSession<?,?>)connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
@@ -88,7 +88,7 @@ arguments.put("x-filter-jms-selector", "
// create binding
session.bindQueue(queueName, routingKey, FieldTable.convertToFieldTable(arguments),
new AMQShortString("amq.topic"), destination);</pre></div></div><br class="example-break"><p> The following example illustrates the creation of queue binding to topic exchange with JMX
- interface using the ManagedExchange interface. </p><div class="example"><a name="idp7167856"></a><p class="title"><b>Example 9.4. Binding a queue using JMX</b></p><div class="example-contents"><pre class="programlisting">Map<String, Object> environment = new HashMap<String, Object>();
+ interface using the ManagedExchange interface. </p><div class="example"><a name="idp7177760"></a><p class="title"><b>Example 9.4. Binding a queue using JMX</b></p><div class="example-contents"><pre class="programlisting">Map<String, Object> environment = new HashMap<String, Object>();
environment.put(JMXConnector.CREDENTIALS, new String[] {"admin","password"});
// Connect to service
@@ -193,7 +193,7 @@ topicExchange.createNewBinding("queue",
Message group support is specified by providing one or more of the following settings
in the arguments map that is used when declaring the queue (e.g. when calling
<code class="code">AMQSession.createQueue()</code>).
- </p><div class="table"><a name="idp6981056"></a><p class="title"><b>Table 9.2. Queue Declare Message Group Configuration Arguments</b></p><div class="table-contents"><table summary="Queue Declare Message Group Configuration Arguments" border="1"><colgroup><col><col></colgroup><thead><tr><th>Key</th><th>Value</th></tr></thead><tbody><tr><td>qpid.group_header_key</td><td>The name of the message header that holds the group identifier value.
+ </p><div class="table"><a name="idp6909936"></a><p class="title"><b>Table 9.2. Queue Declare Message Group Configuration Arguments</b></p><div class="table-contents"><table summary="Queue Declare Message Group Configuration Arguments" border="1"><colgroup><col><col></colgroup><thead><tr><th>Key</th><th>Value</th></tr></thead><tbody><tr><td>qpid.group_header_key</td><td>The name of the message header that holds the group identifier value.
The values in this header may be of any supported type (i.e. not just strings).
</td></tr><tr><td>qpid.shared_msg_group</td><td>Provide a value of "1" to switch on
<a class="link" href="Java-Broker-Queues.html#Java-Broker-Queues-OtherTypes-BrokerRole" title="9.1.7.2. The Role of the Broker in Message Grouping">C++ compatibility mode</a></td></tr></tbody></table></div></div><p><br class="table-break">
Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Runtime-Disk-Space-Management.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Runtime-Disk-Space-Management.html?rev=1530450&r1=1530449&r2=1530450&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Runtime-Disk-Space-Management.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Runtime-Disk-Space-Management.html Tue Oct 8 22:32:49 2013
@@ -3,7 +3,7 @@
into the Java Messaging Broker, causing producers to be flow-controlled when they
attempt to send messages to an overfull queue. Qpid 0.18 introduced a similar
mechanism triggered by an overfull persistent message store on a virtual host.
- </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="Java-Broker-Runtime-Disk-Space-Management-Producer-Flow-Control-ServerConfiguration"></a>12.3.1.2. Server Configuration</h4></div></div></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idp7464208"></a>Configuring a Queue to use flow control</h5></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="Java-Broker-Runtime-Disk-Space-Management-Producer-Flow-Control-ServerConfiguration"></a>12.3.1.2. Server Configuration</h4></div></div></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idp7613408"></a>Configuring a Queue to use flow control</h5></div></div></div><p>
Flow control is enabled on a producer when it sends a message to a Queue
which is "overfull". The producer flow control will be rescinded when all
Queues on which a producer is blocking become "underfull". A Queue is defined
@@ -17,7 +17,7 @@
Where no flowResumeCapacity is set, the flowResumeCapacity is set to be equal
to the capacity. Where no capacity is set, capacity is defaulted to 0 meaning
there is no capacity limit.
- </p><div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Important</h3>Flow control can be configured globally for all virtual hosts by specifying threshold values for Broker flow control attributes.</div><div class="section"><div class="titlepage"><div><div><h6 class="title"><a name="idp7468368"></a>Broker Log Messages</h6></div></div></div><p>
+ </p><div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Important</h3>Flow control can be configured globally for all virtual hosts by specifying threshold values for Broker flow control attributes.</div><div class="section"><div class="titlepage"><div><div><h6 class="title"><a name="idp7617536"></a>Broker Log Messages</h6></div></div></div><p>
There are four new Broker log messages that may occur if flow control through queue capacity limits is enabled.
Firstly, when a capacity limited queue becomes overfull, a log message similar to the following is produced
</p><pre class="programlisting">
@@ -28,7 +28,7 @@ MESSAGE [con:2(guest@anonymous(713889609
MESSAGE [vh(/test)/qu(MyQueue)] [vh(/test)/qu(MyQueue)] QUE-1004 : Underfull : Size : 600 bytes, Resume Capacity : 800
</pre><p>And for every channel which becomes unblocked you will see a message similar to: </p><pre class="programlisting">
MESSAGE [con:2(guest@anonymous(713889609)/test)/ch:1] [con:2(guest@anonymous(713889609)/test)/ch:1] CHN-1006 : Flow Control Removed
- </pre><p>Obviously the details of connection, virtual host, queue, size, capacity, etc would depend on the configuration in use.</p></div></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idp7688528"></a>Disk quota-based flow control</h5></div></div></div><p>
+ </pre><p>Obviously the details of connection, virtual host, queue, size, capacity, etc would depend on the configuration in use.</p></div></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idp7679616"></a>Disk quota-based flow control</h5></div></div></div><p>
Since version 0.18 of Qpid Broker, flow control can be triggered when a
configured disk quota is exceeded. This is supported by the BDB and Derby message stores.
</p><p>
@@ -49,7 +49,7 @@ MESSAGE [con:2(guest@anonymous(713889609
cannot guarantee that the disk space limit will not be exceeded. If several concurrent
transactions are started before the limit is reached, which collectively cause the limit
to be exceeded, the broker may allow all of them to be committed.
- </p><div class="section"><div class="titlepage"><div><div><h6 class="title"><a name="idp7694096"></a>Broker Log Messages for quota flow control</h6></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h6 class="title"><a name="idp7685184"></a>Broker Log Messages for quota flow control</h6></div></div></div><p>
There are 2 new broker log messages that may occur if flow control through disk quota limits is enabled.
When the virtual host is blocked due to exceeding of the disk quota limit the following message
appears in the broker log
@@ -92,6 +92,6 @@ WARN Message send delayed by 10s due t
</p><pre class="programlisting">
-Dqpid.flow_control_wait_failure=60000
-Dqpid.flow_control_wait_notify_period=10000
- </pre><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idp7704944"></a>Older Clients</h5></div></div></div><p>
+ </pre><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idp7696032"></a>Older Clients</h5></div></div></div><p>
The flow control feature was first added to the Java broker/client in the 0.6 release. If an older client connects to the broker then the flow control commands will be ignored by it and it will not be blocked. So to fully benefit from this feature both Client and Broker need to be at least version 0.6.
</p></div></div></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Java-Broker-Runtime-Alerts.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="Java-Broker-Runtime.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="Java-Broker-Runtime-Producer-Transaction-Timeout.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">12.2. Alerts </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 12.4. Producer Transaction Timeout</td></tr></table></div><div class="main_text_area_bottom"></div></div></div></body></html>
Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Security.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Security.html?rev=1530450&r1=1530449&r2=1530450&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Security.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Security.html Tue Oct 8 22:32:49 2013
@@ -116,7 +116,7 @@ com.sun.security.jgss.accept {
row in providers grid on Broker tab) the list of existing credentials is displayed on the tab with the buttons "Add User"
and "Delete Users" to add new user credentials and delete the existing user credentials respectively.
On clicking into user name on Users grid the pop-up dialog to change the password is displayed.
- </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp7535392"></a>11.1.5.1. Plain Password File Format</h4></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp7548672"></a>11.1.5.1. Plain Password File Format</h4></div></div></div><p>
The user credentials are stored on the single file line as user name and user password pairs separated by colon character.
</p><pre class="programlisting">
# password file format
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org