You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@qpid.apache.org by ro...@apache.org on 2012/11/25 22:04:51 UTC
svn commit: r1413417 [1/12] - in /qpid/site/docs/books/trunk:
AMQP-Messaging-Broker-CPP-Book/html/ AMQP-Messaging-Broker-CPP-Book/pdf/
AMQP-Messaging-Broker-Java-Book/html/ AMQP-Messaging-Broker-Java-Book/pdf/
Programming-In-Apache-Qpid/html/ Programmi...
Author: robbie
Date: Sun Nov 25 21:04:37 2012
New Revision: 1413417
URL: http://svn.apache.org/viewvc?rev=1413417&view=rev
Log:
NO-JIRA: publish the latest trunk docs
Added:
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Concepts-Authentication-Providers.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Concepts-Exchanges.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Concepts-Other-Services.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Concepts-Ports.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Concepts-Protocols.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Concepts-Queues.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Concepts.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Configuring-And-Managing-JMX.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Configuring-And-Managing-Other-Tooling.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Configuring-And-Managing-REST-API.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Configuring-And-Managing-Web-Console.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Configuring-And-Managing.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Exchanges.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Getting-Started-CommandLine.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Getting-Started-LogFile.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Getting-Started-Starting-Stopping-Unix.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Getting-Started-Starting-Stopping-Windows.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Getting-Started.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-Backup.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-ClientFailover.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-Configuration.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-DisasterRecovery.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-DiskSpace.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-DurabilityGuarantee.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-JMXAPI.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-MigrationFromNonHA.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-Monitoring-cluster.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-MultiNodeCluster.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-Network-Requirements.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-OfferingsOfJavaBroker.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-Performance.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-Security.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-TwoNodeCluster.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Installation-Download.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Installation-InstallationUnix.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Installation-InstallationWindows.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Installation-Prerequistes.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Installation.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Introduction.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Miscellaneous.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Queues-OtherTypes.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Queues.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Runtime-Alerts.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Runtime-Disk-Space-Management.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Runtime.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Security-ACLs.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Security-Authentication-Providers.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Security-Group-Providers.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Security-SSL.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Security.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Stores-BDB-Store.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Stores-Derby-Store.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Stores-HA-BDB-Store.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Stores-SQL-Store.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Stores.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Virtual-Hosts.html
Removed:
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Configuring-ACLS.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Configuring-Authentication-Mechanisms.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Configuring-Group-Providers.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/High-Availability.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/How-to-Tune-M3-Java-Broker-Performance.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Configuration-Guide.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Debug-Logging.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Environment-Variables.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-General-User-Guides.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/OtherQueueTypes.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Qpid-Java-Broker-Config-File.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Qpid-Java-Broker-HowTos.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Qpid-Java-Broker-Virtualhosts-Config.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Qpid-Java-Build-HowTo.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Qpid-Java-FAQ.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Qpid-Java-Log4j.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Qpid-Java-SSL.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Qpid-Troubleshooting-Guide.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/pr01.html
Modified:
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/AMQP-Compatibility.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/QpidInteroperabilityDocumentation-QpidInteroperabilityDocumentation.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/Using-message-groups.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s06.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s14.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch02s02.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch02s03.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/chap-Messaging_User_Guide-Active_Active_Cluster.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/chap-Messaging_User_Guide-Active_Passive_Cluster.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/chap-Messaging_User_Guide-Security.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/chapter-Managing-CPP-Broker.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/index.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/producer-flow-control.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/pdf/AMQP-Messaging-Broker-CPP-Book.pdf
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/index.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/pdf/AMQP-Messaging-Broker-Java-Book.pdf
qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/QpidJNDI.html
qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/QpidWCF.html
qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch03s03.html
qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch03s06.html
qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch04s02.html
qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch04s03.html
qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch04s04.html
qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch04s05.html
qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch05.html
qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch05s02.html
qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/ch05s03.html
qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/index.html
qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/section-JMS-Logging.html
qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/html/section-JMS-MapMessage.html
qpid/site/docs/books/trunk/Programming-In-Apache-Qpid/pdf/Programming-In-Apache-Qpid.pdf
Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/AMQP-Compatibility.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/AMQP-Compatibility.html?rev=1413417&r1=1413416&r2=1413417&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/AMQP-Compatibility.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/AMQP-Compatibility.html Sun Nov 25 21:04:37 2012
@@ -39,7 +39,7 @@
</p><p>
Here is a matrix that describes the different versions supported
by each release. The status symbols are interpreted as follows:
- </p><div class="variablelist"><dl><dt><span class="term">Y</span></dt><dd><p>supported</p></dd><dt><span class="term">N</span></dt><dd><p>unsupported</p></dd><dt><span class="term">IP</span></dt><dd><p>in progress</p></dd><dt><span class="term">P</span></dt><dd><p>planned</p></dd></dl></div><div class="table"><a name="id2519283"></a><p class="title"><b>Table 1.12. AMQP Version Support by Qpid Release</b></p><div class="table-contents"><table summary="AMQP Version Support by Qpid Release" border="1"><colgroup><col><col><col><col><col><col></colgroup><tbody><tr><td>
+ </p><div class="variablelist"><dl><dt><span class="term">Y</span></dt><dd><p>supported</p></dd><dt><span class="term">N</span></dt><dd><p>unsupported</p></dd><dt><span class="term">IP</span></dt><dd><p>in progress</p></dd><dt><span class="term">P</span></dt><dd><p>planned</p></dd></dl></div><div class="table"><a name="id2520724"></a><p class="title"><b>Table 1.15. AMQP Version Support by Qpid Release</b></p><div class="table-contents"><table summary="AMQP Version Support by Qpid Release" border="1"><colgroup><col><col><col><col><col><col></colgroup><tbody><tr><td>
Component
</td><td>
Spec
@@ -248,7 +248,7 @@
table by AMQP specification version
</h3></div></div></div><p>
Above table represented in another format.
- </p><div class="table"><a name="id2546097"></a><p class="title"><b>Table 1.13. AMQP Version Support - alternate format</b></p><div class="table-contents"><table summary="AMQP Version Support - alternate format" border="1"><colgroup><col><col><col><col><col></colgroup><tbody><tr><td>
+ </p><div class="table"><a name="id2541660"></a><p class="title"><b>Table 1.16. AMQP Version Support - alternate format</b></p><div class="table-contents"><table summary="AMQP Version Support - alternate format" border="1"><colgroup><col><col><col><col><col></colgroup><tbody><tr><td>
Â
</td><td>
release
Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/QpidInteroperabilityDocumentation-QpidInteroperabilityDocumentation.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/QpidInteroperabilityDocumentation-QpidInteroperabilityDocumentation.html?rev=1413417&r1=1413416&r2=1413417&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/QpidInteroperabilityDocumentation-QpidInteroperabilityDocumentation.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/QpidInteroperabilityDocumentation-QpidInteroperabilityDocumentation.html Sun Nov 25 21:04:37 2012
@@ -16,7 +16,7 @@
This table list the various SASL mechanisms that each component
supports. The version listed shows when this
functionality was added to the product.
- </p><div class="table"><a name="id2549899"></a><p class="title"><b>Table 1.14. SASL Mechanism Support</b></p><div class="table-contents"><table summary="SASL Mechanism Support" border="1"><colgroup><col><col><col><col><col><col><col></colgroup><tbody><tr><td>
+ </p><div class="table"><a name="id2510544"></a><p class="title"><b>Table 1.17. SASL Mechanism Support</b></p><div class="table-contents"><table summary="SASL Mechanism Support" border="1"><colgroup><col><col><col><col><col><col><col></colgroup><tbody><tr><td>
Component
</td><td>
ANONYMOUS
@@ -157,7 +157,7 @@
</h4></div></div></div><p>
There have been some custom mechanisms added to our
implementations.
- </p><div class="table"><a name="id2500548"></a><p class="title"><b>Table 1.15. SASL Custom Mechanisms</b></p><div class="table-contents"><table summary="SASL Custom Mechanisms" border="1"><colgroup><col><col><col></colgroup><tbody><tr><td>
+ </p><div class="table"><a name="id2531929"></a><p class="title"><b>Table 1.18. SASL Custom Mechanisms</b></p><div class="table-contents"><table summary="SASL Custom Mechanisms" border="1"><colgroup><col><col><col></colgroup><tbody><tr><td>
Component
</td><td>
AMQPLAIN
@@ -205,7 +205,7 @@
M2
</td><td>
Â
- </td></tr></tbody></table></div></div><br class="table-break"><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2505626"></a>AMQPLAIN</h5></div></div></div><p></p></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2505452"></a>CRAM-MD5-HASHED</h5></div></div></div><p>
+ </td></tr></tbody></table></div></div><br class="table-break"><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2552109"></a>AMQPLAIN</h5></div></div></div><p></p></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2513008"></a>CRAM-MD5-HASHED</h5></div></div></div><p>
The Java SASL implementations require that you have the password
of the user to validate the incoming request. This then means
that the user's password must be stored on disk. For this to be
Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/Using-message-groups.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/Using-message-groups.html?rev=1413417&r1=1413416&r2=1413417&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/Using-message-groups.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/Using-message-groups.html Sun Nov 25 21:04:37 2012
@@ -118,26 +118,26 @@
Message group support can be enabled on a queue using the
<span class="command"><strong>qpid-config</strong></span> command line tool. The following options should be
provided when adding a new queue:
- </p><div class="table"><a name="id2529435"></a><p class="title"><b>Table 1.16. qpid-config options for creating message group queues</b></p><div class="table-contents"><table summary="qpid-config options for creating message group queues" border="1"><colgroup><col><col></colgroup><thead><tr><th>Option</th><th>Description</th></tr></thead><tbody><tr><td>--group-header=<em class="replaceable"><code>header-name</code></em></td><td>Enable message group support for this queue. Specify name of application header that holds the group identifier.</td></tr><tr><td>--shared-groups</td><td>Enforce ordered message group consumption across multiple consumers.</td></tr></tbody></table></div></div><p><br class="table-break">
+ </p><div class="table"><a name="id2505679"></a><p class="title"><b>Table 1.19. qpid-config options for creating message group queues</b></p><div class="table-contents"><table summary="qpid-config options for creating message group queues" border="1"><colgroup><col><col></colgroup><thead><tr><th>Option</th><th>Description</th></tr></thead><tbody><tr><td>--group-header=<em class="replaceable"><code>header-name</code></em></td><td>Enable message group support for this queue. Specify name of application header that holds the group identifier.</td></tr><tr><td>--shared-groups</td><td>Enforce ordered message group consumption across multiple consumers.</td></tr></tbody></table></div></div><p><br class="table-break">
</p><p>
Message group support may also be specified in the
<span class="command"><strong>queue.declare</strong></span> method via the <span class="command"><strong>arguments</strong></span>
parameter map, or using the messaging address syntax. The following keys must be
provided in the arguments map to enable message group support on a queue:
- </p><div class="table"><a name="id2504917"></a><p class="title"><b>Table 1.17. Queue Declare/Address Syntax Message Group Configuration Arguments</b></p><div class="table-contents"><table summary="Queue Declare/Address Syntax 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>string - key for message header that holds the group identifier value</td></tr><tr><td>qpid.shared_msg_group</td><td>1 - enforce ordering across multiple consumers</td></tr></tbody></table></div></div><br class="table-break"><p>
+ </p><div class="table"><a name="id2538666"></a><p class="title"><b>Table 1.20. Queue Declare/Address Syntax Message Group Configuration Arguments</b></p><div class="table-contents"><table summary="Queue Declare/Address Syntax 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>string - key for message header that holds the group identifier value</td></tr><tr><td>qpid.shared_msg_group</td><td>1 - enforce ordering across multiple consumers</td></tr></tbody></table></div></div><br class="table-break"><p>
It is important to note that there is no need to provide the actual group
identifer values that will be used. The broker learns this values as messages are
recieved. Also, there is no practical limit - aside from resource limitations -
to the number of different groups that the broker can track at run time.
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Restrictions</h3><p>
Message grouping is not supported on LVQ or Priority queues.
- </p></div><div class="example"><a name="id2509966"></a><p class="title"><b>Example 1.2. Creating a message group queue via qpid-config</b></p><div class="example-contents"><p>
+ </p></div><div class="example"><a name="id2536899"></a><p class="title"><b>Example 1.2. Creating a message group queue via qpid-config</b></p><div class="example-contents"><p>
This example uses the qpid-config tool to create a message group queue called
"MyMsgQueue". The message header that contains the group identifier will use
the key "GROUP_KEY".
</p><pre class="programlisting">
qpid-config add queue MyMsgQueue --group-header="GROUP_KEY" --shared-groups
- </pre></div></div><br class="example-break"><div class="example"><a name="id2528175"></a><p class="title"><b>Example 1.3. Creating a message group queue using address syntax (C++)</b></p><div class="example-contents"><p>
+ </pre></div></div><br class="example-break"><div class="example"><a name="id2514746"></a><p class="title"><b>Example 1.3. Creating a message group queue using address syntax (C++)</b></p><div class="example-contents"><p>
This example uses the messaging address syntax to create a message group queue
with the same configuration as the previous example.
</p><pre class="programlisting">
@@ -150,7 +150,7 @@ sender = session.createSender("MyMsgQueu
Default Group
</h4></div></div></div><p>
Should a message without a group identifier arrive at a queue configured for message grouping, the broker assigns the message to the default group. Therefore, all such "unidentified" messages are considered by the broker as part of the same group. The name of the default group is <span class="command"><strong>"qpid.no-group"</strong></span>. This default can be overridden by suppling a different value to the broker configuration item <span class="command"><strong>"default-message-group"</strong></span>:
- </p><div class="example"><a name="id2538058"></a><p class="title"><b>Example 1.4. Overriding the default message group identifier for the broker</b></p><div class="example-contents"><pre class="programlisting">
+ </p><div class="example"><a name="id2549668"></a><p class="title"><b>Example 1.4. Overriding the default message group identifier for the broker</b></p><div class="example-contents"><pre class="programlisting">
qpidd --default-msg-group "EMPTY-GROUP"
</pre></div></div><p><br class="example-break">
</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="QpidInteroperabilityDocumentation-QpidInteroperabilityDocumentation.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch01.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="chap-Messaging_User_Guide-Active_Passive_Cluster.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">1.11. Qpid Interoperability Documentation </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 1.13. Active-passive Messaging Clusters</td></tr></table></div><div class="main_text_area_bottom"></div></div></div></body></html>
Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01.html?rev=1413417&r1=1413416&r2=1413417&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01.html Sun Nov 25 21:04:37 2012
@@ -28,7 +28,7 @@
Cheat Sheet for configuring Exchange Options
</a></span></dt><dd><dl><dt><span class="section"><a href="ch01s03.html#CheatSheetforconfiguringExchangeOptions-ConfiguringExchangeOptions">1.3.1.
Configuring Exchange Options
- </a></span></dt></dl></dd><dt><span class="section"><a href="chap-Messaging_User_Guide-Broker_Federation.html">1.4. Broker Federation</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Messaging_User_Guide-Broker_Federation.html#sect-Messaging_User_Guide-Broker_Federation-Message_Routes">1.4.1. Message Routes</a></span></dt><dt><span class="section"><a href="chap-Messaging_User_Guide-Broker_Federation.html#sect-Messaging_User_Guide-Broker_Federation-Federation_Topologies">1.4.2. Federation Topologies</a></span></dt><dt><span class="section"><a href="chap-Messaging_User_Guide-Broker_Federation.html#sect-Messaging_User_Guide-Broker_Federation-Federation_among_High_Availability_Message_Clusters">1.4.3. Federation among High Availability Message Clusters</a></span></dt><dt><span class="section"><a href="chap-Messaging_User_Guide-Broker_Federation.html#sect-Messaging_User_Guide-Broker_Federation-The_qpid_route_Utility">1.4.4. The qpid-route Utility</a></span></dt>
</dl></dd><dt><span class="section"><a href="chap-Messaging_User_Guide-Security.html">1.5. Security</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Messaging_User_Guide-Security.html#sect-Messaging_User_Guide-Security-User_Authentication">1.5.1. User Authentication</a></span></dt><dt><span class="section"><a href="chap-Messaging_User_Guide-Security.html#sect-Messaging_User_Guide-Security-Authorization">1.5.2. Authorization</a></span></dt><dt><span class="section"><a href="chap-Messaging_User_Guide-Security.html#sect-Messaging_User_Guide-Security-Encryption_using_SSL">1.5.3. Encryption using SSL</a></span></dt></dl></dd><dt><span class="section"><a href="ch01s06.html">1.6. LVQ - Last Value Queue</a></span></dt><dd><dl><dt><span class="section"><a href="ch01s06.html#LVQ-UnderstandingLVQ">1.6.1. Understanding LVQ</a></span></dt><dt><span class="section"><a href="ch01s06.html#LVQ-Creating">1.6.2. Creating a Last Value Queue</a></span></dt><dt><span class="section"
><a href="ch01s06.html#LVQ-Example">1.6.3. LVQ Example</a></span></dt><dt><span class="section"><a href="ch01s06.html#LVQ-Deprecated">1.6.4. Deprecated LVQ Modes</a></span></dt></dl></dd><dt><span class="section"><a href="queue-state-replication.html">1.7.
+ </a></span></dt></dl></dd><dt><span class="section"><a href="chap-Messaging_User_Guide-Broker_Federation.html">1.4. Broker Federation</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Messaging_User_Guide-Broker_Federation.html#sect-Messaging_User_Guide-Broker_Federation-Message_Routes">1.4.1. Message Routes</a></span></dt><dt><span class="section"><a href="chap-Messaging_User_Guide-Broker_Federation.html#sect-Messaging_User_Guide-Broker_Federation-Federation_Topologies">1.4.2. Federation Topologies</a></span></dt><dt><span class="section"><a href="chap-Messaging_User_Guide-Broker_Federation.html#sect-Messaging_User_Guide-Broker_Federation-Federation_among_High_Availability_Message_Clusters">1.4.3. Federation among High Availability Message Clusters</a></span></dt><dt><span class="section"><a href="chap-Messaging_User_Guide-Broker_Federation.html#sect-Messaging_User_Guide-Broker_Federation-The_qpid_route_Utility">1.4.4. The qpid-route Utility</a></span></dt>
</dl></dd><dt><span class="section"><a href="chap-Messaging_User_Guide-Security.html">1.5. Security</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Messaging_User_Guide-Security.html#sect-Messaging_User_Guide-Security-User_Authentication">1.5.1. User Authentication</a></span></dt><dt><span class="section"><a href="chap-Messaging_User_Guide-Security.html#sect-Messaging_User_Guide-Security-Authorization">1.5.2. Authorization</a></span></dt><dt><span class="section"><a href="chap-Messaging_User_Guide-Security.html#sect-Messaging_User_Guide-Authorization-Specifying_ACL_Quotas">1.5.3. User Connection and Queue Quotas</a></span></dt><dt><span class="section"><a href="chap-Messaging_User_Guide-Security.html#sect-Messaging_User_Guide-Security-Encryption_using_SSL">1.5.4. Encryption using SSL</a></span></dt></dl></dd><dt><span class="section"><a href="ch01s06.html">1.6. LVQ - Last Value Queue</a></span></dt><dd><dl><dt><span class="section"><a href="ch01s06.html#LVQ-Un
derstandingLVQ">1.6.1. Understanding LVQ</a></span></dt><dt><span class="section"><a href="ch01s06.html#LVQ-Creating">1.6.2. Creating a Last Value Queue</a></span></dt><dt><span class="section"><a href="ch01s06.html#LVQ-Example">1.6.3. LVQ Example</a></span></dt><dt><span class="section"><a href="ch01s06.html#LVQ-Deprecated">1.6.4. Deprecated LVQ Modes</a></span></dt></dl></dd><dt><span class="section"><a href="queue-state-replication.html">1.7.
Queue State Replication
</a></span></dt><dd><dl><dt><span class="section"><a href="queue-state-replication.html#queuestatereplication-AsynchronousReplicationofQueueState">1.7.1.
Asynchronous
@@ -61,7 +61,7 @@
Well Behaved Consumers
</a></span></dt><dt><span class="section"><a href="Using-message-groups.html#usingmessagegroups-BrokerConfig">1.12.5.
Broker Configuration
- </a></span></dt></dl></dd><dt><span class="section"><a href="chap-Messaging_User_Guide-Active_Passive_Cluster.html">1.13. Active-passive Messaging Clusters</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Messaging_User_Guide-Active_Passive_Cluster.html#id2527186">1.13.1. Overview</a></span></dt><dt><span class="section"><a href="chap-Messaging_User_Guide-Active_Passive_Cluster.html#id2521283">1.13.2. Virtual IP Addresses</a></span></dt><dt><span class="section"><a href="chap-Messaging_User_Guide-Active_Passive_Cluster.html#id2507913">1.13.3. Configuring the Brokers</a></span></dt><dt><span class="section"><a href="chap-Messaging_User_Guide-Active_Passive_Cluster.html#id2519604">1.13.4. The Cluster Resource Manager</a></span></dt><dt><span class="section"><a href="chap-Messaging_User_Guide-Active_Passive_Cluster.html#id2521752">1.13.5. Configuring <span class="command"><strong>rgmanager</strong></span> as resource manager</a></span></dt><dt><span class="s
ection"><a href="chap-Messaging_User_Guide-Active_Passive_Cluster.html#id2530379">1.13.6. Broker Administration Tools</a></span></dt><dt><span class="section"><a href="chap-Messaging_User_Guide-Active_Passive_Cluster.html#ha-creating-replicated">1.13.7. Creating replicated queues and exchanges</a></span></dt><dt><span class="section"><a href="chap-Messaging_User_Guide-Active_Passive_Cluster.html#id2534176">1.13.8. Client Connection and Fail-over</a></span></dt><dt><span class="section"><a href="chap-Messaging_User_Guide-Active_Passive_Cluster.html#id2511498">1.13.9. Security.</a></span></dt><dt><span class="section"><a href="chap-Messaging_User_Guide-Active_Passive_Cluster.html#id2520122">1.13.10. Integrating with other Cluster Resource Managers</a></span></dt></dl></dd><dt><span class="section"><a href="ch01s14.html">1.14. Queue Replication with the HA module</a></span></dt></dl></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name=
"section-Running-a-Qpid-CPP-Broker"></a>1.1.Â
+ </a></span></dt></dl></dd><dt><span class="section"><a href="chap-Messaging_User_Guide-Active_Passive_Cluster.html">1.13. Active-passive Messaging Clusters</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Messaging_User_Guide-Active_Passive_Cluster.html#id2504335">1.13.1. Overview</a></span></dt><dt><span class="section"><a href="chap-Messaging_User_Guide-Active_Passive_Cluster.html#id2556078">1.13.2. Virtual IP Addresses</a></span></dt><dt><span class="section"><a href="chap-Messaging_User_Guide-Active_Passive_Cluster.html#id2552113">1.13.3. Configuring the Brokers</a></span></dt><dt><span class="section"><a href="chap-Messaging_User_Guide-Active_Passive_Cluster.html#id2502605">1.13.4. The Cluster Resource Manager</a></span></dt><dt><span class="section"><a href="chap-Messaging_User_Guide-Active_Passive_Cluster.html#id2538674">1.13.5. Configuring <span class="command"><strong>rgmanager</strong></span> as resource manager</a></span></dt><dt><span class="s
ection"><a href="chap-Messaging_User_Guide-Active_Passive_Cluster.html#id2548120">1.13.6. Broker Administration Tools</a></span></dt><dt><span class="section"><a href="chap-Messaging_User_Guide-Active_Passive_Cluster.html#ha-creating-replicated">1.13.7. Creating replicated queues and exchanges</a></span></dt><dt><span class="section"><a href="chap-Messaging_User_Guide-Active_Passive_Cluster.html#id2500900">1.13.8. Client Connection and Fail-over</a></span></dt><dt><span class="section"><a href="chap-Messaging_User_Guide-Active_Passive_Cluster.html#id2505763">1.13.9. Security.</a></span></dt><dt><span class="section"><a href="chap-Messaging_User_Guide-Active_Passive_Cluster.html#id2553256">1.13.10. Integrating with other Cluster Resource Managers</a></span></dt></dl></dd><dt><span class="section"><a href="ch01s14.html">1.14. Queue Replication with the HA module</a></span></dt></dl></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name=
"section-Running-a-Qpid-CPP-Broker"></a>1.1.Â
Running a Qpid C++ Broker
</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="RASC-BuildingtheCppBrokerandClientLibraries"></a>1.1.1.Â
Building the
Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s06.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s06.html?rev=1413417&r1=1413416&r2=1413417&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s06.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s06.html Sun Nov 25 21:04:37 2012
@@ -1,6 +1,6 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>1.6. LVQ - Last Value Queue</title><link rel="stylesheet" href="css/style.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.73.2"><link rel="start" href="index.html" title="AMQP Messaging Broker (Implemented in C++)"><link rel="up" href="ch01.html" title="Chapter 1. Running the AMQP Messaging Broker"><link rel="prev" href="chap-Messaging_User_Guide-Security.html" title="1.5. Security"><link rel="next" href="queue-state-replication.html" title="1.7. Queue State Replication"></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">Ho
me</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 (Implemented in C++)</a></span> > <span class="breadcrumb-link"><a href="ch01.html">
Running the AMQP Messaging Broker
- </a></span> > <span class="breadcrumb-node">LVQ - Last Value Queue</span></DIV><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2542179"></a>1.6. LVQ - Last Value Queue</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="LVQ-UnderstandingLVQ"></a>1.6.1. Understanding LVQ</h3></div></div></div><p>
+ </a></span> > <span class="breadcrumb-node">LVQ - Last Value Queue</span></DIV><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2497817"></a>1.6. LVQ - Last Value Queue</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="LVQ-UnderstandingLVQ"></a>1.6.1. Understanding LVQ</h3></div></div></div><p>
A Last Value Queue is configured with the name of a message header that
is used as a key. The queue behaves as a normal FIFO queue with the
exception that when a message is enqueued, any other message in the
Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s14.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s14.html?rev=1413417&r1=1413416&r2=1413417&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s14.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s14.html Sun Nov 25 21:04:37 2012
@@ -1,6 +1,6 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>1.14. Queue Replication with the HA module</title><link rel="stylesheet" href="css/style.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.73.2"><link rel="start" href="index.html" title="AMQP Messaging Broker (Implemented in C++)"><link rel="up" href="ch01.html" title="Chapter 1. Running the AMQP Messaging Broker"><link rel="prev" href="chap-Messaging_User_Guide-Active_Passive_Cluster.html" title="1.13. Active-passive Messaging Clusters"><link rel="next" href="chapter-Managing-CPP-Broker.html" title="Chapter 2. Managing the AMQP Messaging 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_b
ody"><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_t
op"></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 (Implemented in C++)</a></span> > <span class="breadcrumb-link"><a href="ch01.html">
Running the AMQP Messaging Broker
- </a></span> > <span class="breadcrumb-node">Queue Replication with the HA module</span></DIV><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2519799"></a>1.14. Queue Replication with the HA module</h2></div></div></div><p>
+ </a></span> > <span class="breadcrumb-node">Queue Replication with the HA module</span></DIV><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2522901"></a>1.14. Queue Replication with the HA module</h2></div></div></div><p>
As well as support for an active-passive cluster, the <code class="filename">ha</code> module
also allows you to replicate individual queues. The <em class="firstterm">original</em>
queue is used as normal. The <em class="firstterm">replica</em> queue is updated
Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch02s02.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch02s02.html?rev=1413417&r1=1413416&r2=1413417&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch02s02.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch02s02.html Sun Nov 25 21:04:37 2012
@@ -2,7 +2,7 @@
Managing the AMQP Messaging Broker
</a></span> > <span class="breadcrumb-node">
Qpid Management Framework
- </span></DIV><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2521161"></a>2.2.Â
+ </span></DIV><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2526753"></a>2.2.Â
Qpid Management Framework
</h2></div></div></div><div class="itemizedlist"><ul><li><p>
<a class="xref" href="ch02s02.html#QpidManagementFramework-WhatIsQMF" title="2.2.1. What Is QMF">Section 2.2.1, â
@@ -193,7 +193,7 @@
</p><p>
The XML syntax for <property> and <statistic> have
the following XML-attributes:
- </p><div class="table"><a name="id2519179"></a><p class="title"><b>Table 2.1. XML Attributes for QMF Properties and Statistics</b></p><div class="table-contents"><table summary="XML Attributes for QMF Properties and Statistics" border="1"><colgroup><col><col><col><col></colgroup><tbody><tr><td>
+ </p><div class="table"><a name="id2515109"></a><p class="title"><b>Table 2.1. XML Attributes for QMF Properties and Statistics</b></p><div class="table-contents"><table summary="XML Attributes for QMF Properties and Statistics" border="1"><colgroup><col><col><col><col></colgroup><tbody><tr><td>
Attribute
</td><td>
<property>
@@ -329,7 +329,7 @@
data types. The data types are based on the rich data typing
system provided by the AMQP messaging protocol. The following
table describes the data types available for QMF:
- </p><div class="table"><a name="id2553476"></a><p class="title"><b>Table 2.2. QMF Datatypes</b></p><div class="table-contents"><table summary="QMF Datatypes" border="1"><colgroup><col><col></colgroup><tbody><tr><td>
+ </p><div class="table"><a name="id2502148"></a><p class="title"><b>Table 2.2. QMF Datatypes</b></p><div class="table-contents"><table summary="QMF Datatypes" border="1"><colgroup><col><col></colgroup><tbody><tr><td>
QMF Type
</td><td>
Description
@@ -413,7 +413,7 @@
attributes of different types. The following table enumerates the
types available in the XML format, which QMF types they map to,
and other special handling that occurs.
- </p><div class="table"><a name="id2515475"></a><p class="title"><b>Table 2.3. XML Schema Mapping for QMF Types</b></p><div class="table-contents"><table summary="XML Schema Mapping for QMF Types" border="1"><colgroup><col><col><col><col></colgroup><tbody><tr><td>
+ </p><div class="table"><a name="id2517777"></a><p class="title"><b>Table 2.3. XML Schema Mapping for QMF Types</b></p><div class="table-contents"><table summary="XML Schema Mapping for QMF Types" border="1"><colgroup><col><col><col><col></colgroup><tbody><tr><td>
XML Type
</td><td>
QMF Type
Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch02s03.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch02s03.html?rev=1413417&r1=1413416&r2=1413417&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch02s03.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch02s03.html Sun Nov 25 21:04:37 2012
@@ -2,7 +2,7 @@
Managing the AMQP Messaging Broker
</a></span> > <span class="breadcrumb-node">
QMF Python Console Tutorial
- </span></DIV><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2502284"></a>2.3.Â
+ </span></DIV><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="id2547489"></a>2.3.Â
QMF Python Console Tutorial
</h2></div></div></div><div class="itemizedlist"><ul><li><p>
<a class="xref" href="ch02s03.html#QMFPythonConsoleTutorial-PrerequisiteInstallQpidMessaging" title="2.3.1. Prerequisite - Install Qpid Messaging">Section 2.3.1, â
@@ -404,7 +404,7 @@ OK
methods. Any number of these methods may be overridden by the
console application. Any method that is not overridden defaults
to a null handler which takes no action when invoked.
- </p><div class="table"><a name="id2505397"></a><p class="title"><b>Table 2.4. QMF Python Console Class Methods</b></p><div class="table-contents"><table summary="QMF Python Console Class Methods" border="1"><colgroup><col><col><col></colgroup><tbody><tr><td>
+ </p><div class="table"><a name="id2507304"></a><p class="title"><b>Table 2.4. QMF Python Console Class Methods</b></p><div class="table-contents"><table summary="QMF Python Console Class Methods" border="1"><colgroup><col><col><col></colgroup><tbody><tr><td>
Method
</td><td>
Arguments
Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/chap-Messaging_User_Guide-Active_Active_Cluster.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/chap-Messaging_User_Guide-Active_Active_Cluster.html?rev=1413417&r1=1413416&r2=1413417&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/chap-Messaging_User_Guide-Active_Active_Cluster.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/chap-Messaging_User_Guide-Active_Active_Cluster.html Sun Nov 25 21:04:37 2012
@@ -53,7 +53,7 @@
If you are using SELinux, the qpidd process and OpenAIS must have the same SELinux context, or else SELinux must be set to permissive mode. If both qpidd and OpenAIS are run as services, they have the same SELinux context. If both OpenAIS and qpidd are run as user processes, they have the same SELinux context. If one is run as a service, and the other is run as a user process, they have different SELinux contexts.
</p></div><p>
The following options are available for clustering:
- </p><div class="table"><a name="tabl-Messaging_User_Guide-Starting_a_Broker_in_a_Cluster-Options_for_High_Availability_Messaging_Cluster"></a><p class="title"><b>Table 1.9. Options for High Availability Messaging Cluster</b></p><div class="table-contents"><table summary="Options for High Availability Messaging Cluster" border="1"><colgroup><col align="left"><col align="left"></colgroup><thead><tr><th colspan="2" align="center">
+ </p><div class="table"><a name="tabl-Messaging_User_Guide-Starting_a_Broker_in_a_Cluster-Options_for_High_Availability_Messaging_Cluster"></a><p class="title"><b>Table 1.12. Options for High Availability Messaging Cluster</b></p><div class="table-contents"><table summary="Options for High Availability Messaging Cluster" border="1"><colgroup><col align="left"><col align="left"></colgroup><thead><tr><th colspan="2" align="center">
Options for High Availability Messaging Cluster
</th></tr></thead><tbody><tr><td align="left">
<span class="command"><strong>--cluster-name <em class="replaceable"><code>NAME</code></em></strong></span>
Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/chap-Messaging_User_Guide-Active_Passive_Cluster.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/chap-Messaging_User_Guide-Active_Passive_Cluster.html?rev=1413417&r1=1413416&r2=1413417&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/chap-Messaging_User_Guide-Active_Passive_Cluster.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/chap-Messaging_User_Guide-Active_Passive_Cluster.html Sun Nov 25 21:04:37 2012
@@ -1,6 +1,6 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>1.13. Active-passive Messaging Clusters</title><link rel="stylesheet" href="css/style.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.73.2"><link rel="start" href="index.html" title="AMQP Messaging Broker (Implemented in C++)"><link rel="up" href="ch01.html" title="Chapter 1. Running the AMQP Messaging Broker"><link rel="prev" href="Using-message-groups.html" title="1.12. Using Message Groups"><link rel="next" href="ch01s14.html" title="1.14. Queue Replication with the HA module"></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 h
ref="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 h
ref="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 (Implemented in C++)</a></span> > <span class="breadcrumb-link"><a href="ch01.html">
Running the AMQP Messaging Broker
- </a></span> > <span class="breadcrumb-node">Active-passive Messaging Clusters</span></DIV><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="chap-Messaging_User_Guide-Active_Passive_Cluster"></a>1.13. Active-passive Messaging Clusters</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2527186"></a>1.13.1. Overview</h3></div></div></div><p>
+ </a></span> > <span class="breadcrumb-node">Active-passive Messaging Clusters</span></DIV><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="chap-Messaging_User_Guide-Active_Passive_Cluster"></a>1.13. Active-passive Messaging Clusters</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2504335"></a>1.13.1. Overview</h3></div></div></div><p>
The High Availability (HA) module provides
<em class="firstterm">active-passive</em>, <em class="firstterm">hot-standby</em>
@@ -20,23 +20,31 @@
This approach relies on an external <em class="firstterm">cluster resource manager</em>
to detect failures, choose the new primary and handle network partitions. <a class="ulink" href="https://fedorahosted.org/cluster/wiki/RGManager" target="_top">Rgmanager</a> is supported
initially, but others may be supported in the future.
- </p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2510022"></a>1.13.1.1. Avoiding message loss</h4></div></div></div><p>
+ </p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2529756"></a>1.13.1.1. Avoiding message loss</h4></div></div></div><p>
In order to avoid message loss, the primary broker <span class="emphasis"><em>delays
- acknowledgment</em></span> of messages received from clients until the
- message has been replicated to and acknowledged by all of the back-up
+ acknowledgment</em></span> of messages received from clients until the message has
+ been replicated to and acknowledged by all of the back-up brokers. This means that
+ all <span class="emphasis"><em>acknowledged</em></span> messages are safely stored on all the backup
brokers.
</p><p>
- Clients buffer unacknowledged messages and re-send them in the event of
- a fail-over.
- <sup>[<a name="id2506437" href="#ftn.id2506437" class="footnote">1</a>]</sup>
- If the primary crashes before a message is replicated to
- all the backups, the client will re-send the message when it fails over
- to the new primary.
+ Clients keep <span class="emphasis"><em>unacknowledged</em></span> messages in a buffer
+ <sup>[<a name="id2532801" href="#ftn.id2532801" class="footnote">1</a>]</sup>
+ until they are acknowledged by the primary. If the primary fails, clients will
+ fail-over to the new primary and <span class="emphasis"><em>re-send</em></span> all their
+ unacknowledged messages.
+ <sup>[<a name="id2521293" href="#ftn.id2521293" class="footnote">2</a>]</sup>
+ </p><p>
+ So if the primary crashes, all the <span class="emphasis"><em>acknowledged</em></span> messages will
+ be available on the backup that takes over as the new primary. The
+ <span class="emphasis"><em>unacknowledged</em></span> messages will be re-sent by the clients. Thus
+ no messages are lost.
+ </p><p>
</p><p>
Note that this means it is possible for messages to be
- <span class="emphasis"><em>duplicated</em></span>. In the event of a failure it is
- possible for a message to be both received by the backup that becomes
- the new primary <span class="emphasis"><em>and</em></span> re-sent by the client.
+ <span class="emphasis"><em>duplicated</em></span>. In the event of a failure it is possible for a
+ message to received by the backup that becomes the new primary
+ <span class="emphasis"><em>and</em></span> re-sent by the client. The application must take steps
+ to identify and eliminate duplicates.
</p><p>
When a new primary is promoted after a fail-over it is initially in
"recovering" mode. In this mode, it delays acknowledgment of messages
@@ -55,7 +63,7 @@
The newly-promoted primary, waiting for backups to connect and catch up.
</p></dd><dt><span class="term">Active</span></dt><dd><p>
The active primary broker with all backups connected and caught-up.
- </p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554434"></a>1.13.1.2. Replacing the old cluster module</h4></div></div></div><p>
+ </p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2551131"></a>1.13.1.2. Replacing the old cluster module</h4></div></div></div><p>
The High Availability (HA) module replaces the previous
<em class="firstterm">active-active</em> cluster module. The new active-passive
approach has several advantages compared to the existing active-active cluster
@@ -67,25 +75,18 @@
It is more portable: in environments that don't support corosync, it can be
integrated with a resource manager available in that environment.
</li><li>
- Replication to a <em class="firstterm">disaster recovery</em> site can be handled as
- simply another node in the cluster, it does not require a separate replication
- mechanism.
- </li><li>
It can take advantage of features provided by the resource manager, for example
virtual IP addresses.
</li><li>
Improved performance and scalability due to better use of multiple CPUs
</li></ul></div><p>
- </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2502041"></a>1.13.1.3. Limitations</h4></div></div></div><div class="itemizedlist"><ul><li>
- Transactional changes to queue state are not replicated atomically. If the
- primary crashes during a transaction, it is possible that the backup could
- contain only part of the changes introduced by a transaction.
- </li><li>
- Not yet integrated with the persistent store. A persistent broker must have its
- store erased before joining an existing cluster. If the entire cluster fails,
- there are no tools to help identify the most recent store. In the future a
- persistent broker will be able to use its stored messages to avoid downloading
- messages from the primary when joining a cluster.
+ </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2538501"></a>1.13.1.3. Limitations</h4></div></div></div><p>
+ There are a number of known limitations in the current preview implementation. These
+ will be fixed in the production versions.
+ </p><div class="itemizedlist"><ul><li>
+ Transactional changes to queue state are not replicated atomically. If the primary crashes
+ during a transaction, it is possible that the backup could contain only part of the
+ changes introduced by a transaction.
</li><li>
Configuration changes (creating or deleting queues, exchanges and bindings) are
replicated asynchronously. Management tools used to make changes will consider
@@ -99,8 +100,8 @@
</li><li>
Federated links <span class="emphasis"><em>from</em></span> the primary will be lost in fail over,
they will not be re-connected to the new primary. Federation links
- <span class="emphasis"><em>to</em></span> the primary can fail over.
- </li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2521283"></a>1.13.2. Virtual IP Addresses</h3></div></div></div><p>
+ <span class="emphasis"><em>to</em></span> the primary will fail over.
+ </li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556078"></a>1.13.2. Virtual IP Addresses</h3></div></div></div><p>
Some resource managers (including <span class="command"><strong>rgmanager</strong></span>) support
<em class="firstterm">virtual IP addresses</em>. A virtual IP address is an IP
address that can be relocated to any of the nodes in a cluster. The
@@ -112,10 +113,10 @@
A virtual IP address can be used by clients and backup brokers to connect
to the primary. The following sections will explain how to configure
virtual IP addresses for clients or brokers.
- </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2507913"></a>1.13.3. Configuring the Brokers</h3></div></div></div><p>
+ </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2552113"></a>1.13.3. Configuring the Brokers</h3></div></div></div><p>
The broker must load the <code class="filename">ha</code> module, it is loaded by
default. The following broker options are available for the HA module.
- </p><div class="table"><a name="ha-broker-options"></a><p class="title"><b>Table 1.18. Broker Options for High Availability Messaging Cluster</b></p><div class="table-contents"><table summary="Broker Options for High Availability Messaging Cluster" border="1"><colgroup><col align="left"><col align="left"></colgroup><thead><tr><th colspan="2" align="center">
+ </p><div class="table"><a name="ha-broker-options"></a><p class="title"><b>Table 1.21. Broker Options for High Availability Messaging Cluster</b></p><div class="table-contents"><table summary="Broker Options for High Availability Messaging Cluster" border="1"><colgroup><col align="left"><col align="left"></colgroup><thead><tr><th colspan="2" align="center">
Options for High Availability Messaging Cluster
</th></tr></thead><tbody><tr><td align="left">
<code class="literal">ha-cluster <em class="replaceable"><code>yes|no</code></em></code>
@@ -126,18 +127,18 @@
</td><td align="left">
<p>
The URL
- <sup>[<a name="id2499186" href="#ftn.id2499186" class="footnote">a</a>]</sup>
- used by cluster brokers to connect to each other. The URL can
- contain a list of all the broker addresses or it can contain a single
- virtual IP address. If a list is used it is comma separated, for example
+ <sup>[<a name="ha-url-grammar" href="#ftn.ha-url-grammar" class="footnote">a</a>]</sup>
+ used by cluster brokers to connect to each other. The URL should
+ contain a comma separated list of the broker addresses, rather than a
+ virtual IP address. For example:
<code class="literal">amqp:node1.exaple.com,node2.exaple.com,node3.exaple.com</code>
</p>
</td></tr><tr><td align="left"><code class="literal">ha-public-url <em class="replaceable"><code>URL</code></em></code> </td><td align="left">
<p>
- The URL that is advertised to clients. This defaults to the
- <code class="literal">ha-brokers-url</code> URL above, and has the same format. A
- virtual IP address is recommended for the public URL as it simplifies
- deployment and hides changes to the cluster membership from clients.
+ The URL <sup>[<a href="chap-Messaging_User_Guide-Active_Passive_Cluster.html#ftn.ha-url-grammar" class="footnoteref">a</a>]</sup> used by clients to connect to the cluster. This can be a list or
+ a single virtual IP address. A virtual IP address is recommended as it
+ simplifies deployment. If not specified this defaults to the value of
+ <code class="literal">ha-brokers-url</code>.
</p>
<p>
This option allows you to put client traffic on a different network from
@@ -170,7 +171,12 @@
be. If you want brokers to fail over quickly you can set this to a
fraction of a second, for example: 0.1.
</p>
- </td></tr></tbody><tbody class="footnotes"><tr><td colspan="2"><div class="footnote"><p><sup>[<a name="ftn.id2499186" href="#id2499186" class="para">a</a>] </sup>
+ </td></tr><tr><td align="left"><code class="literal">link-heartbeat-interval <em class="replaceable"><code>SECONDS</code></em></code></td><td align="left">
+ <p>
+ Heartbeat interval for replication links. The link will be assumed broken
+ if there is no heartbeat for twice the interval.
+ </p>
+ </td></tr></tbody><tbody class="footnotes"><tr><td colspan="2"><div class="footnote"><p><sup>[<a name="ftn.ha-url-grammar" href="#ha-url-grammar" class="para">a</a>] </sup>
The full format of the URL is given by this grammar:
<pre class="programlisting">
url = ["amqp:"][ user ["/" password] "@" ] addr ("," addr)*
@@ -182,7 +188,7 @@ ssl_addr = "ssl:" host [":" port]'
</p></div></td></tr></tbody></table></div></div><br class="table-break"><p>
To configure a HA cluster you must set at least <code class="literal">ha-cluster</code> and
<code class="literal">ha-brokers-url</code>.
- </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2519604"></a>1.13.4. The Cluster Resource Manager</h3></div></div></div><p>
+ </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2502605"></a>1.13.4. The Cluster Resource Manager</h3></div></div></div><p>
Broker fail-over is managed by a <em class="firstterm">cluster resource
manager</em>. An integration with <a class="ulink" href="https://fedorahosted.org/cluster/wiki/RGManager" target="_top">rgmanager</a> is
provided, but it is possible to integrate with other resource managers.
@@ -208,7 +214,7 @@ ssl_addr = "ssl:" host [":" port]'
network partition divide a cluster into two sub-groups which cannot see each other.
Usually a <em class="firstterm">quorum</em> voting algorithm is used that disables nodes
in the inquorate sub-group.
- </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2521752"></a>1.13.5. Configuring <span class="command"><strong>rgmanager</strong></span> as resource manager</h3></div></div></div><p>
+ </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2538674"></a>1.13.5. Configuring <span class="command"><strong>rgmanager</strong></span> as resource manager</h3></div></div></div><p>
This section assumes that you are already familiar with setting up and configuring
clustered services using <span class="command"><strong>cman</strong></span> and
<span class="command"><strong>rgmanager</strong></span>. It will show you how to configure an active-passive,
@@ -329,7 +335,7 @@ NOTE: fencing is not shown, you must con
original node fails. Running the <code class="literal">qpidd-primary</code> script
does not start a new broker process, it promotes the existing broker to
become the primary.
- </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2530379"></a>1.13.6. Broker Administration Tools</h3></div></div></div><p>
+ </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2548120"></a>1.13.6. Broker Administration Tools</h3></div></div></div><p>
Normally, clients are not allowed to connect to a backup broker. However
management tools are allowed to connect to a backup brokers. If you use
these tools you <span class="emphasis"><em>must not</em></span> add or remove messages from
@@ -369,7 +375,17 @@ NOTE: fencing is not shown, you must con
<code class="literal">node</code> entry to the address like this:
</p><pre class="programlisting">
"myqueue;{create:always,node:{x-declare:{arguments:{'qpid.replicate':all}}}}"
- </pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2534176"></a>1.13.8. Client Connection and Fail-over</h3></div></div></div><p>
+ </pre><p>
+ There are some built-in exchanges created automatically by the broker, these
+ exchangs are never replicated. The built-in exchanges are the default (nameless)
+ exchange, the AMQP standard exchanges (<code class="literal">amq.direct, amq.topic, amq.fanout</code> and
+ <code class="literal">amq.match</code>) and the management exchanges (<code class="literal">qpid.management, qmf.default.direct</code> and
+ <code class="literal">qmf.default.topic</code>)
+ </p><p>
+ Note that if you bind a replicated queue to one of these exchanges, the
+ binding wil <span class="emphasis"><em>not</em></span> be replicated, so the queue will not
+ have the binding after a fail-over.
+ </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2500900"></a>1.13.8. Client Connection and Fail-over</h3></div></div></div><p>
Clients can only connect to the primary broker. Backup brokers
automatically reject any connection attempt by a client.
</p><p>
@@ -380,7 +396,7 @@ NOTE: fencing is not shown, you must con
</li><li>
The URL contains a single <em class="firstterm">virtual IP address</em>
that is assigned to the primary broker by the resource manager.
- <sup>[<a name="id2506281" href="#ftn.id2506281" class="footnote">2</a>]</sup></li></ul></div><p>
+ <sup>[<a name="id2553483" href="#ftn.id2553483" class="footnote">3</a>]</sup></li></ul></div><p>
In the first case, clients will repeatedly re-try each address in the URL
until they successfully connect to the primary. In the second case the
resource manager will assign the virtual IP address to the primary broker,
@@ -409,9 +425,9 @@ NOTE: fencing is not shown, you must con
a client you need to specify the address(es) and set the
<code class="literal">reconnect</code> property to <code class="literal">true</code>. The
following sub-sections show how to connect each type of client.
- </p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2521107"></a>1.13.8.1. C++ clients</h4></div></div></div><p>
+ </p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2549105"></a>1.13.8.1. C++ clients</h4></div></div></div><p>
With the C++ client, you specify multiple cluster addresses in a single URL
- <sup>[<a name="id2518032" href="#ftn.id2518032" class="footnote">3</a>]</sup>
+ <sup>[<a name="id2507910" href="#ftn.id2507910" class="footnote">4</a>]</sup>
You also need to specify the connection option
<code class="literal">reconnect</code> to be true. For example:
</p><pre class="programlisting">
@@ -423,7 +439,7 @@ NOTE: fencing is not shown, you must con
</p><pre class="programlisting">
qpid::messaging::Connection c("node1,node2,node3","{reconnect:true,heartbeat:10}");
</pre><p>
- </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2538815"></a>1.13.8.2. Python clients</h4></div></div></div><p>
+ </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2514781"></a>1.13.8.2. Python clients</h4></div></div></div><p>
With the python client, you specify <code class="literal">reconnect=True</code>
and a list of <em class="replaceable"><code>host:port</code></em> addresses as
<code class="literal">reconnect_urls</code> when calling
@@ -437,7 +453,7 @@ NOTE: fencing is not shown, you must con
connection via the 'heartbeat' option. For example:
</p><pre class="programlisting">
connection = qpid.messaging.Connection.establish("node1", reconnect=True, reconnect_urls=["node1", "node2", "node3"], heartbeat=10)
- </pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2504672"></a>1.13.8.3. Java JMS Clients</h4></div></div></div><p>
+ </pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2521191"></a>1.13.8.3. Java JMS Clients</h4></div></div></div><p>
In Java JMS clients, client fail-over is handled automatically if it is
enabled in the connection. You can configure a connection to use
fail-over using the <span class="command"><strong>failover</strong></span> property:
@@ -455,14 +471,14 @@ NOTE: fencing is not shown, you must con
In a Connection URL, heartbeat is set using the <span class="command"><strong>idle_timeout</strong></span> property, which is an integer corresponding to the heartbeat period in seconds. For instance, the following line from a JNDI properties file sets the heartbeat time out to 3 seconds:
</p><pre class="screen">
connectionfactory.qpidConnectionfactory = amqp://guest:guest@clientid/test?brokerlist='tcp://localhost:5672',idle_timeout=3
- </pre></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2511498"></a>1.13.9. Security.</h3></div></div></div><p>
+ </pre></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2505763"></a>1.13.9. Security.</h3></div></div></div><p>
You can secure your cluster using the authentication and authorization features
described in <a class="xref" href="chap-Messaging_User_Guide-Security.html" title="1.5. Security">Section 1.5, âSecurityâ</a>.
</p><p>
Backup brokers connect to the primary broker and subscribe for management
events and queue contents. You can specify the identity used to connect
to the primary with the following options:
- </p><div class="table"><a name="ha-broker-security-options"></a><p class="title"><b>Table 1.19. Security options for High Availability Messaging Cluster</b></p><div class="table-contents"><table summary="Security options for High Availability Messaging Cluster" border="1"><colgroup><col align="left"><col align="left"></colgroup><thead><tr><th colspan="2" align="center">
+ </p><div class="table"><a name="ha-broker-security-options"></a><p class="title"><b>Table 1.22. Security options for High Availability Messaging Cluster</b></p><div class="table-contents"><table summary="Security options for High Availability Messaging Cluster" border="1"><colgroup><col align="left"><col align="left"></colgroup><thead><tr><th colspan="2" align="center">
Security options for High Availability Messaging Cluster
</th></tr></thead><tbody><tr><td align="left">
<p><code class="literal">ha-username <em class="replaceable"><code>USER</code></em></code></p>
@@ -476,7 +492,7 @@ NOTE: fencing is not shown, you must con
</td></tr></tbody></table></div></div><br class="table-break"><p>
This identity is also used to authorize actions taken on the backup broker to replicate
from the primary, for example to create queues or exchanges.
- </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2520122"></a>1.13.10. Integrating with other Cluster Resource Managers</h3></div></div></div><p>
+ </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553256"></a>1.13.10. Integrating with other Cluster Resource Managers</h3></div></div></div><p>
To integrate with a different resource manager you must configure it to:
</p><div class="itemizedlist"><ul><li>Start a qpidd process on each node of the cluster.</li><li>Restart qpidd if it crashes.</li><li>Promote exactly one of the brokers to primary.</li><li>Detect a failure and promote a new primary.</li></ul></div><p>
</p><p>
@@ -499,12 +515,17 @@ NOTE: fencing is not shown, you must con
You can also use <span class="command"><strong>qpid-ha</strong></span> to manually examine and promote brokers. This
can be useful for testing failover scenarios without having to set up a full resource manager,
or to simulate a cluster on a single node. For deployment, a resource manager is required.
- </p></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2506437" href="#id2506437" class="para">1</a>] </sup>
+ </p></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id2532801" href="#id2532801" class="para">1</a>] </sup>
+ You can control the maximum number of messages in the buffer by setting the
+ client's <code class="literal">capacity</code>. For details of how to set the capacity
+ in client code see "Using the Qpid Messaging API" in
+ <em class="citetitle">Programming in Apache Qpid</em>.
+ </p></div><div class="footnote"><p><sup>[<a name="ftn.id2521293" href="#id2521293" class="para">2</a>] </sup>
Clients must use "at-least-once" reliability to enable re-send of unacknowledged
messages. This is the default behavior, no options need be set to enable it. For
details of client addressing options see "Using the Qpid Messaging API"
- in <em class="citetitle">Programming in Apache Qpid</em>
- </p></div><div class="footnote"><p><sup>[<a name="ftn.id2506281" href="#id2506281" class="para">2</a>] </sup>Only if the resource manager supports virtual IP addresses</p></div><div class="footnote"><p><sup>[<a name="ftn.id2518032" href="#id2518032" class="para">3</a>] </sup>
+ in <em class="citetitle">Programming in Apache Qpid</em>.
+ </p></div><div class="footnote"><p><sup>[<a name="ftn.id2553483" href="#id2553483" class="para">3</a>] </sup>Only if the resource manager supports virtual IP addresses</p></div><div class="footnote"><p><sup>[<a name="ftn.id2507910" href="#id2507910" class="para">4</a>] </sup>
The full grammar for the URL is:
</p><pre class="programlisting">
url = ["amqp:"][ user ["/" password] "@" ] addr ("," addr)*
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org