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 2010/12/05 22:59:26 UTC

svn commit: r1042462 [3/12] - in /qpid/site/docs/books/0.8: ./ AMQP-Messaging-Broker-CPP-Book/ AMQP-Messaging-Broker-CPP-Book/html/ AMQP-Messaging-Broker-CPP-Book/html/images/ AMQP-Messaging-Broker-CPP-Book/html/images/jmx_console/ AMQP-Messaging-Broke...

Added: qpid/site/docs/books/0.8/AMQP-Messaging-Broker-CPP-Book/html/ch01s08.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/0.8/AMQP-Messaging-Broker-CPP-Book/html/ch01s08.html?rev=1042462&view=auto
==============================================================================
--- qpid/site/docs/books/0.8/AMQP-Messaging-Broker-CPP-Book/html/ch01s08.html (added)
+++ qpid/site/docs/books/0.8/AMQP-Messaging-Broker-CPP-Book/html/ch01s08.html Sun Dec  5 21:59:22 2010
@@ -0,0 +1,239 @@
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>1.8. High Availability Messaging Clusters</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" 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="ch01s07.html" title="1.7.  Queue State Replication"><link rel="next" href="ch01s09.html" title="1.9.  ACL"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.8. High Availability Messaging Clusters</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01s07.html">Prev</a> </td><th width="60%" align="center">Chapter 1.             
+      Running the AMQP Messaging Broker
+    </th><td width="20%" align="right"> <a accesskey="n" href="ch01s09.html">Next</a></td></tr></table><hr></div><div class="section" title="1.8. High Availability Messaging Clusters"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="chap-Messaging_User_Guide-High_Availability_Messaging_Clusters"></a>1.8. High Availability Messaging Clusters</h2></div></div></div><p>
+		High Availability Messaging Clusters provide fault tolerance by ensuring that every broker in a <em class="firstterm">cluster</em> has the same queues, exchanges, messages, and bindings, and allowing a client to <em class="firstterm">fail over</em> to a new broker and continue without any loss of messages if the current broker fails or becomes unavailable. Because all brokers are automatically kept in a consistent state, clients can connect to and use any broker in a cluster. Any number of messaging brokers can be run as one <em class="firstterm">cluster</em>, and brokers can be added to or removed from a cluster while it is in use.
+	</p><p>
+		High Availability Messaging Clusters are implemented using using the <a class="ulink" href="http://www.openais.org/" target="_top">OpenAIS Cluster Framework</a>.
+	</p><p>
+		An OpenAIS daemon runs on every machine in the cluster, and these daemons communicate using multicast on a particular address. Every qpidd process in a cluster joins a named group that is automatically synchronized using OpenAIS Closed Process Groups (CPG) &#8212; the qpidd processes multicast events to the named group, and CPG ensures that each qpidd process receives all the events in the same sequence. All members get an identical sequence of events, so they can all update their state consistently.
+	</p><p>
+		Two messaging brokers are in the same cluster if 
+		</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
+					They run on hosts in the same OpenAIS cluster; that is, OpenAIS is configured with the same mcastaddr, mcastport and bindnetaddr, and
+				</p></li><li class="listitem"><p>
+					They use the same cluster name.
+				</p></li></ol></div><p>
+
+	</p><p>
+		High Availability Clustering has a cost: in order to allow each broker in a cluster to continue the work of any other broker, a cluster must replicate state for all brokers in the cluster. Because of this, the brokers in a cluster should normally be on a LAN; there should be fast and reliable connections between brokers. Even on a LAN, using multiple brokers in a cluster is somewhat slower than using a single broker without clustering. This may be counter-intuitive for people who are used to clustering in the context of High Performance Computing or High Throughput Computing, where clustering increases performance or throughput.
+	</p><p>
+		High Availability Messaging Clusters should be used together with Red Hat Clustering Services (RHCS); without RHCS, clusters are vulnerable to the "split-brain" condition, in which a network failure splits the cluster into two sub-clusters that cannot communicate with each other. See the documentation on the <span class="command"><strong>--cluster-cman</strong></span> option for details on running using RHCS with High Availability Messaging Clusters. See the <a class="ulink" href="http://sources.redhat.com/cluster/wiki" target="_top">CMAN Wiki</a> for more detail on CMAN and split-brain conditions. Use the <span class="command"><strong>--cluster-cman</strong></span> option to enable RHCS when starting the broker.
+	</p><div class="section" title="1.8.1. Starting a Broker in a Cluster"><div class="titlepage"><div><div><h3 class="title"><a name="sect-Messaging_User_Guide-High_Availability_Messaging_Clusters-Starting_a_Broker_in_a_Cluster"></a>1.8.1. Starting a Broker in a Cluster</h3></div></div></div><p>
+			Clustering is implemented using the <code class="filename">cluster.so</code> module, which is loaded by default when you start a broker. To run brokers in a cluster, make sure they all use the same OpenAIS mcastaddr, mcastport, and bindnetaddr. All brokers in a cluster must also have the same cluster name &#8212; specify the cluster name in <code class="filename">qpidd.conf</code>:
+		</p><pre class="screen">cluster-name="local_test_cluster"
+</pre><p>
+			On RHEL6, you must create the file <code class="filename">/etc/corosync/uidgid.d/qpidd</code> to tell Corosync the name of the user running the broker.By default, the user is qpidd:
+		</p><pre class="programlisting">
+uidgid {
+   uid: qpidd
+   gid: qpidd
+}
+</pre><p>
+			On RHEL5, the primary group for the process running qpidd must be the ais group. If you are running qpidd as a service, it is run as the <span class="command"><strong>qpidd</strong></span> user, which is already in the ais group. If you are running the broker from the command line, you must ensure that the primary group for the user running qpidd is ais. You can set the primary group using <span class="command"><strong>newgrp</strong></span>:
+		</p><pre class="screen">$ newgrp ais
+</pre><p>
+			You can then run the broker from the command line, specifying the cluster name as an option.
+		</p><pre class="screen">[jonathan@localhost]$ qpidd --cluster-name="local_test_cluster"
+</pre><p>
+			All brokers in a cluster must have identical configuration, with a few exceptions noted below. They must load the same set of plug-ins, and have matching configuration files and command line arguments. The should also have identical ACL files and SASL databases if these are used. If one broker uses persistence, all must use persistence &#8212; a mix of transient and persistent brokers is not allowed. Differences in configuration can cause brokers to exit the cluster. For instance, if different ACL settings allow a client to access a queue on broker A but not on broker B, then publishing to the queue will succeed on A and fail on B, so B will exit the cluster to prevent inconsistency.
+		</p><p>
+			The following settings can differ for brokers on a given cluster:
+		</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
+					logging options
+				</p></li><li class="listitem"><p>
+					cluster-url &#8212; if set, it will be different for each broker.
+				</p></li><li class="listitem"><p>
+					port &#8212; brokers can listen on different ports.
+				</p></li></ul></div><p>
+			The qpid log contains entries that record significant clustering events, e.g. when a broker becomes a member of a cluster, the membership of a cluster is changed, or an old journal is moved out of the way. For instance, the following message states that a broker has been added to a cluster as the first node:
+		</p><pre class="screen">
+2009-07-09 18:13:41 info 127.0.0.1:1410(READY) member update: 127.0.0.1:1410(member) 
+2009-07-09 18:13:41 notice 127.0.0.1:1410(READY) first in cluster
+</pre><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
+				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.3. 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>
+						</td><td align="left">
+							Name of the Messaging Cluster to join. A Messaging Cluster consists of all brokers started with the same cluster-name and openais configuration.
+						</td></tr><tr><td align="left">
+							<span class="command"><strong>--cluster-size <em class="replaceable"><code>N</code></em></strong></span>
+						</td><td align="left">
+							Wait for at least N initial members before completing cluster initialization and serving clients. Use this option in a persistent cluster so all brokers in a persistent cluster can exchange the status of their persistent store and do consistency checks before serving clients.
+						</td></tr><tr><td align="left">
+							<span class="command"><strong>--cluster-url <em class="replaceable"><code>URL</code></em></strong></span>
+						</td><td align="left">
+							An AMQP URL containing the local address that the broker advertizes to clients for fail-over connections. This is different for each host. By default, all local addresses for the broker are advertized. You only need to set this if 
+							<div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
+										Your host has more than one active network interface, and
+									</p></li><li class="listitem"><p>
+										You want to restrict client fail-over to a specific interface or interfaces.
+									</p></li></ol></div>
+							 Each broker in the cluster is specified using the form: <span class="command"><strong> url = ["amqp:"][ user ["/" password] "@" ] protocol_addr *("," protocol_addr) protocol_addr = tcp_addr / rmda_addr / ssl_addr / ... tcp_addr = ["tcp:"] host [":" port] rdma_addr = "rdma:" host [":" port] ssl_addr = "ssl:" host [":" port]</strong></span> In most cases, only one address is advertized, but more than one address can be specified in if the machine running the broker has more than one network interface card, and you want to allow clients to connect using multiple network interfaces. Use a comma delimiter (",") to separate brokers in the URL. Examples: 
+							<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
+										<span class="command"><strong>amqp:tcp:192.168.1.103:5672</strong></span> advertizes a single address to the broker for failover.
+									</p></li><li class="listitem"><p>
+										<span class="command"><strong>amqp:tcp:192.168.1.103:5672,tcp:192.168.1.105:5672</strong></span> advertizes two different addresses to the broker for failover, on two different network interfaces.
+									</p></li></ul></div>
+
+						</td></tr><tr><td align="left">
+							<span class="command"><strong>--cluster-cman</strong></span>
+						</td><td align="left">
+							<p>
+								CMAN protects against the "split-brain" condition, in which a network failure splits the cluster into two sub-clusters that cannot communicate with each other. When "split-brain" occurs, each of the sub-clusters can access shared resources without knowledge of the other sub-cluster, resulting in corrupted cluster integrity.
+							</p>
+							 <p>
+								To avoid "split-brain", CMAN uses the notion of a "quorum". If more than half the cluster nodes are active, the cluster has quorum and can act. If half (or fewer) nodes are active, the cluster does not have quorum, and all cluster activity is stopped. There are other ways to define the quorum for particular use cases (e.g. a cluster of only 2 members), see the <a class="ulink" href="http://sources.redhat.com/cluster/wiki" target="_top">CMAN Wiki</a> 
+for more detail.
+							</p>
+							 <p>
+								When enabled, the broker will wait until it belongs to a quorate cluster before accepting client connections. It continually monitors the quorum status and shuts down immediately if the node it runs on loses touch with the quorum.
+							</p>
+
+						</td></tr><tr><td align="left">
+							--cluster-username
+						</td><td align="left">
+							SASL username for connections between brokers.
+						</td></tr><tr><td align="left">
+							--cluster-password
+						</td><td align="left">
+							SASL password for connections between brokers.
+						</td></tr><tr><td align="left">
+							--cluster-mechanism
+						</td><td align="left">
+							SASL authentication mechanism for connections between brokers
+						</td></tr></tbody></table></div></div><br class="table-break"><p>
+			If a broker is unable to establish a connection to another broker in the cluster, the log will contain SASL errors, e.g:
+		</p><pre class="screen">2009-aug-04 10:17:37 info SASL: Authentication failed: SASL(-13): user not found: Password verification failed
+</pre><p>
+			You can set the SASL user name and password used to connect to other brokers using the <span class="command"><strong>cluster-username</strong></span> and <span class="command"><strong>cluster-password</strong></span> properties when you start the broker. In most environment, it is easiest to create an account with the same user name and password on each broker in the cluster, and use these as the <span class="command"><strong>cluster-username</strong></span> and <span class="command"><strong>cluster-password</strong></span>. You can also set the SASL mode using <span class="command"><strong>cluster-mechanism</strong></span>. Remember that any mechanism you enable for broker-to-broker communication can also be used by a client, so do not enable <span class="command"><strong>cluster-mechanism=ANONYMOUS</strong></span> in a secure environment.
+		</p><p>
+			Once the cluster is running, run <span class="command"><strong>qpid-cluster</strong></span> to make sure that the brokers are running as one cluster. See the following section for details.
+		</p><p>
+			If the cluster is correctly configured, queues and messages are replicated to all brokers in the cluster, so an easy way to test the cluster is to run a program that routes messages to a queue on one broker, then connect to a different broker in the same cluster and read the messages to make sure they have been replicated. The <span class="command"><strong>drain</strong></span> and <span class="command"><strong>spout</strong></span> programs can be used for this test.
+		</p></div><div class="section" title="1.8.2. qpid-cluster"><div class="titlepage"><div><div><h3 class="title"><a name="sect-Messaging_User_Guide-High_Availability_Messaging_Clusters-qpid_cluster"></a>1.8.2. qpid-cluster</h3></div></div></div><p>
+			<span class="command"><strong>qpid-cluster</strong></span> is a command-line utility that allows you to view information on a cluster and its brokers, disconnect a client connection, shut down a broker in a cluster, or shut down the entire cluster. You can see the options using the <span class="command"><strong>--help</strong></span> option:
+		</p><pre class="screen">$ ./qpid-cluster --help
+</pre><pre class="screen">Usage:  qpid-cluster [OPTIONS] [broker-addr]
+
+             broker-addr is in the form:   [username/password@] hostname | ip-address [:&lt;port&gt;]
+             ex:  localhost, 10.1.1.7:10000, broker-host:10000, guest/guest@localhost
+
+Options:
+          -C [--all-connections]  View client connections to all cluster members
+          -c [--connections] ID   View client connections to specified member
+          -d [--del-connection] HOST:PORT
+                                  Disconnect a client connection
+          -s [--stop] ID          Stop one member of the cluster by its ID
+          -k [--all-stop]         Shut down the whole cluster
+          -f [--force]            Suppress the 'are-you-sure?' prompt
+          -n [--numeric]          Don't resolve names
+</pre><p>
+			Let's connect to a cluster and display basic information about the cluser and its brokers. When you connect to the cluster using <span class="command"><strong>qpid-tool</strong></span>, you can use the host and port for any broker in the cluster. For instance, if a broker in the cluster is running on <code class="filename">localhost</code> on port 6664, you can start <span class="command"><strong>qpid-tool</strong></span> like this:
+		</p><pre class="screen">
+$ qpid-cluster localhost:6664
+</pre><p>
+			Here is the output:
+		</p><pre class="screen">
+  Cluster Name: local_test_cluster
+Cluster Status: ACTIVE
+  Cluster Size: 3
+       Members: ID=127.0.0.1:13143 URL=amqp:tcp:192.168.1.101:6664,tcp:192.168.122.1:6664,tcp:10.16.10.62:6664
+              : ID=127.0.0.1:13167 URL=amqp:tcp:192.168.1.101:6665,tcp:192.168.122.1:6665,tcp:10.16.10.62:6665
+              : ID=127.0.0.1:13192 URL=amqp:tcp:192.168.1.101:6666,tcp:192.168.122.1:6666,tcp:10.16.10.62:6666
+</pre><p>
+			The ID for each broker in cluster is given on the left. For instance, the ID for the first broker in the cluster is <span class="command"><strong>127.0.0.1:13143</strong></span>. The URL in the output is the broker's advertized address. Let's use the ID to shut the broker down using the <span class="command"><strong>--stop</strong></span> command:
+		</p><pre class="screen">$ ./qpid-cluster localhost:6664 --stop 127.0.0.1:13143
+</pre></div><div class="section" title="1.8.3. Failover in Clients"><div class="titlepage"><div><div><h3 class="title"><a name="sect-Messaging_User_Guide-High_Availability_Messaging_Clusters-Failover_in_Clients"></a>1.8.3. Failover in Clients</h3></div></div></div><p>
+			If a client is connected to a broker, the connection fails if the broker crashes or is killed. If heartbeat is enabled for the connection, a connection also fails if the broker hangs, the machine the broker is running on fails, or the network connection to the broker is lost &#8212; the connection fails no later than twice the heartbeat interval.
+		</p><p>
+			When a client's connection to a broker fails, any sent messages that have been acknowledged to the sender will have been replicated to all brokers in the cluster, any received messages that have not yet been acknowledged by the receiving client requeued to all brokers, and the client API notifies the application of the failure by throwing an exception.
+		</p><p>
+			Clients can be configured to automatically reconnect to another broker when it receives such an exception. Any messages that have been sent by the client, but not yet acknowledged as delivered, are resent. Any messages that have been read by the client, but not acknowledged, are delivered to the client.
+		</p><p>
+			TCP is slow to detect connection failures. A client can configure a connection to use a heartbeat to detect connection failure, and can specify a time interval for the heartbeat. If heartbeats are in use, failures will be detected no later than twice the heartbeat interval. The Java JMS client enables hearbeat by default. See the sections on Failover in Java JMS Clients and Failover in C++ Clients for the code to enable heartbeat.
+		</p><div class="section" title="1.8.3.1. Failover in Java JMS Clients"><div class="titlepage"><div><div><h4 class="title"><a name="sect-Messaging_User_Guide-Failover_in_Clients-Failover_in_Java_JMS_Clients"></a>1.8.3.1. Failover in Java JMS Clients</h4></div></div></div><p>
+				In Java JMS clients, client failover is handled automatically if it is enabled in the connection. Any messages that have been sent by the client, but not yet acknowledged as delivered, are resent. Any messages that have been read by the client, but not acknowledged, are sent to the client.
+			</p><p>
+				You can configure a connection to use failover using the <span class="command"><strong>failover</strong></span> property:
+			</p><pre class="screen">
+connectionfactory.qpidConnectionfactory = amqp://guest:guest@clientid/test?brokerlist='tcp://localhost:5672'&amp;failover='failover_exchange'
+</pre><p>
+				This property can take three values:
+			</p><div class="variablelist" title="Failover Modes"><a name="vari-Messaging_User_Guide-Failover_in_Java_JMS_Clients-Failover_Modes"></a><p class="title"><b>Failover Modes</b></p><dl><dt><span class="term">failover_exchange</span></dt><dd><p>
+							If the connection fails, fail over to any other broker in the cluster.
+						</p></dd><dt><span class="term">roundrobin</span></dt><dd><p>
+							If the connection fails, fail over to one of the brokers specified in the <span class="command"><strong>brokerlist</strong></span>.
+						</p></dd><dt><span class="term">singlebroker</span></dt><dd><p>
+							Failover is not supported; the connection is to a single broker only.
+						</p></dd></dl></div><p>
+				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 class="section" title="1.8.3.2. Failover and the Qpid Messaging API"><div class="titlepage"><div><div><h4 class="title"><a name="sect-Messaging_User_Guide-Failover_in_Clients-Failover_and_the_Qpid_Messaging_API"></a>1.8.3.2. Failover and the Qpid Messaging API</h4></div></div></div><p>
+				The Qpid Messaging API also supports automatic reconnection in the event a connection fails. . Senders can also be configured to replay any in-doubt messages (i.e. messages whice were sent but not acknowleged by the broker. See "Connection Options" and "Sender Capacity and Replay" in <em class="citetitle">Programming in Apache Qpid</em> for details.
+			</p><p>
+				In C++ and python clients, heartbeats are disabled by default. You can enable them by specifying a heartbeat interval (in seconds) for the connection via the 'heartbeat' option.
+			</p><p>
+				See "Cluster Failover" in <em class="citetitle">Programming in Apache Qpid</em> for details on how to keep the client aware of cluster membership.
+			</p></div></div><div class="section" title="1.8.4. Error handling in Clusters"><div class="titlepage"><div><div><h3 class="title"><a name="sect-Messaging_User_Guide-High_Availability_Messaging_Clusters-Error_handling_in_Clusters"></a>1.8.4. Error handling in Clusters</h3></div></div></div><p>
+			If a broker crashes or is killed, or a broker machine failure, broker connection failure, or a broker hang is detected, the other brokers in the cluster are notified that it is no longer a member of the cluster. If a new broker is joined to the cluster, it synchronizes with an active broker to obtain the current cluster state; if this synchronization fails, the new broker exit the cluster and aborts.
+		</p><p>
+			If a broker becomes extremely busy and stops responding, it stops accepting incoming work. All other brokers continue processing, and the non-responsive node caches all AIS traffic. When it resumes, the broker completes processes all cached AIS events, then accepts further incoming work. 
+		</p><p>
+			Broker hangs are only detected if the watchdog plugin is loaded and the <span class="command"><strong>--watchdog-interval</strong></span> option is set. The watchdog plug-in kills the qpidd broker process if it becomes stuck for longer than the watchdog interval. In some cases, e.g. certain phases of error resolution, it is possible for a stuck process to hang other cluster members that are waiting for it to send a message. Using the watchdog, the stuck process is terminated and removed from the cluster, allowing other members to continue and clients of the stuck process to fail over to other members.
+		</p><p>
+			Redundancy can also be achieved directly in the AIS network by specifying more than one network interface in the AIS configuration file. This causes Totem to use a redundant ring protocol, which makes failure of a single network transparent.
+		</p><p>
+			Redundancy can be achieved at the operating system level by using NIC bonding, which combines multiple network ports into a single group, effectively aggregating the bandwidth of multiple interfaces into a single connection. This provides both network load balancing and fault tolerance.
+		</p><p>
+			If any broker encounters an error, the brokers compare notes to see if they all received the same error. If not, the broker removes itself from the cluster and shuts itself down to ensure that all brokers in the cluster have consistent state. For instance, a broker may run out of disk space; if this happens, the broker shuts itself down. Examining the broker's log can help determine the error and suggest ways to prevent it from occuring in the future.
+		</p></div><div class="section" title="1.8.5. Persistence in High Availability Message Clusters"><div class="titlepage"><div><div><h3 class="title"><a name="sect-Messaging_User_Guide-High_Availability_Messaging_Clusters-Persistence_in_High_Availability_Message_Clusters"></a>1.8.5. Persistence in High Availability Message Clusters</h3></div></div></div><p>
+			Persistence and clustering are two different ways to provide reliability. Most systems that use a cluster do not enable persistence, but you can do so if you want to ensure that messages are not lost even if the last broker in a cluster fails. A cluster must have all transient or all persistent members, mixed clusters are not allowed. Each broker in a persistent cluster has it's own independent replica of the cluster's state it its store.
+		</p><div class="section" title="1.8.5.1. Clean and Dirty Stores"><div class="titlepage"><div><div><h4 class="title"><a name="sect-Messaging_User_Guide-Persistence_in_High_Availability_Message_Clusters-Clean_and_Dirty_Stores"></a>1.8.5.1. Clean and Dirty Stores</h4></div></div></div><p>
+				When a broker is an active member of a cluster, its store is marked "dirty" because it may be out of date compared to other brokers in the cluster. If a broker leaves a running cluster because it is stopped, it crashes or the host crashes, its store continues to be marked "dirty".
+			</p><p>
+				If the cluster is reduced to a single broker, its store is marked "clean" since it is the only broker making updates. If the cluster is shut down with the command <code class="literal">qpid-cluster -k</code> then all the stores are marked clean.
+			</p><p>
+				When a cluster is initially formed, brokers with clean stores read from their stores. Brokers with dirty stores, or brokers that join after the cluster is running, discard their old stores and initialize a new store with an update from one of the running brokers. The <span class="command"><strong>--truncate</strong></span> option can be used to force a broker to discard all existing stores even if they are clean. (A dirty store is discarded regardless.)
+			</p><p>
+				Discarded stores are copied to a back up directory. The active store is in &lt;data-dir&gt;/rhm. Back-up stores are in &lt;data-dir&gt;/_cluster.bak.&lt;nnnn&gt;/rhm, where &lt;nnnn&gt; is a 4 digit number. A higher number means a more recent backup.
+			</p></div><div class="section" title="1.8.5.2. Starting a persistent cluster"><div class="titlepage"><div><div><h4 class="title"><a name="sect-Messaging_User_Guide-Persistence_in_High_Availability_Message_Clusters-Starting_a_persistent_cluster"></a>1.8.5.2. Starting a persistent cluster</h4></div></div></div><p>
+				When starting a persistent cluster broker, set the cluster-size option to the number of brokers in the cluster. This allows the brokers to wait until the entire cluster is running so that they can synchronize their stored state.
+			</p><p>
+				The cluster can start if:
+			</p><p>
+				</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
+							all members have empty stores, or
+						</p></li><li class="listitem"><p>
+							at least one member has a clean store
+						</p></li></ul></div><p>
+
+			</p><p>
+				All members of the new cluster will be initialized with the state from a clean store.
+			</p></div><div class="section" title="1.8.5.3. Stopping a persistent cluster"><div class="titlepage"><div><div><h4 class="title"><a name="sect-Messaging_User_Guide-Persistence_in_High_Availability_Message_Clusters-Stopping_a_persistent_cluster"></a>1.8.5.3. Stopping a persistent cluster</h4></div></div></div><p>
+				To cleanly shut down a persistent cluster use the command <span class="command"><strong>qpid-cluster -k</strong></span>. This causes all brokers to synchronize their state and mark their stores as "clean" so they can be used when the cluster restarts.
+			</p></div><div class="section" title="1.8.5.4. Starting a persistent cluster with no clean store"><div class="titlepage"><div><div><h4 class="title"><a name="sect-Messaging_User_Guide-Persistence_in_High_Availability_Message_Clusters-Starting_a_persistent_cluster_with_no_clean_store"></a>1.8.5.4. Starting a persistent cluster with no clean store</h4></div></div></div><p>
+				If the cluster has previously had a total failure and there are no clean stores then the brokers will fail to start with the log message <code class="literal">Cannot recover, no clean store.</code> If this happens you can start the cluster by marking one of the stores "clean" as follows:
+			</p><div class="procedure"><ol class="procedure" type="1"><li class="step" title="Step 1"><p>
+						Move the latest store backup into place in the brokers data-directory. The backups end in a 4 digit number, the latest backup is the highest number.
+					</p><pre class="screen">
+ cd &lt;data-dir&gt;
+ mv rhm rhm.bak
+ cp -a _cluster.bak.&lt;nnnn&gt;/rhm .
+</pre></li><li class="step" title="Step 2"><p>
+						Mark the store as clean: 
+</p><pre class="screen">qpid-cluster-store -c &lt;data-dir&gt;</pre><p>
+
+					</p></li></ol></div><p>
+				Now you can start the cluster, all members will be initialized from the store you marked as clean.
+			</p></div><div class="section" title="1.8.5.5. Isolated failures in a persistent cluster"><div class="titlepage"><div><div><h4 class="title"><a name="sect-Messaging_User_Guide-Persistence_in_High_Availability_Message_Clusters-Isolated_failures_in_a_persistent_cluster"></a>1.8.5.5. Isolated failures in a persistent cluster</h4></div></div></div><p>
+				A broker in a persistent cluster may encounter errors that other brokers in the cluster do not; if this happens, the broker shuts itself down to avoid making the cluster state inconsistent. For example a disk failure on one node will result in that node shutting down. Running out of storage capacity can also cause a node to shut down because because the brokers may not run out of storage at exactly the same point, even if they have similar storage configuration. To avoid unnecessary broker shutdowns, make sure the queue policy size of each durable queue is less than the capacity of the journal for the queue.
+			</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch01s07.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="ch01s09.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">1.7. 
+    Queue State Replication
+   </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 1.9. 
+      ACL
+  </td></tr></table></div></body></html>

Added: qpid/site/docs/books/0.8/AMQP-Messaging-Broker-CPP-Book/html/ch01s09.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/0.8/AMQP-Messaging-Broker-CPP-Book/html/ch01s09.html?rev=1042462&view=auto
==============================================================================
--- qpid/site/docs/books/0.8/AMQP-Messaging-Broker-CPP-Book/html/ch01s09.html (added)
+++ qpid/site/docs/books/0.8/AMQP-Messaging-Broker-CPP-Book/html/ch01s09.html Sun Dec  5 21:59:22 2010
@@ -0,0 +1,515 @@
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>1.9.  ACL</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" 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="ch01s08.html" title="1.8. High Availability Messaging Clusters"><link rel="next" href="ch01s10.html" title="1.10.  AMQP compatibility"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.9. 
+      ACL
+  </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01s08.html">Prev</a> </td><th width="60%" align="center">Chapter 1.             
+      Running the AMQP Messaging Broker
+    </th><td width="20%" align="right"> <a accesskey="n" href="ch01s10.html">Next</a></td></tr></table><hr></div><div class="section" title="1.9.  ACL"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="qpid_ACL"></a>1.9. 
+      ACL
+  </h2></div></div></div><div class="section" title="1.9.1.  v2 ACL file format for brokers"><div class="titlepage"><div><div><h3 class="title"><a name="ACL-v2ACLfileformatforbrokers"></a>1.9.1. 
+      v2 ACL file format for brokers
+    </h3></div></div></div><p>
+      This new ACL implementation has been designed for implementation
+      and interoperability on all Qpid brokers. It is currently
+      supported in the following brokers:
+    </p><div class="table"><a name="id2653947"></a><p class="title"><b>Table 1.4. ACL Support in Qpid Broker Versions</b></p><div class="table-contents"><table summary="ACL Support in Qpid Broker Versions" border="1"><colgroup><col><col></colgroup><thead><tr><th>
+                  Broker
+                </th><th>
+                  Version
+                </th></tr></thead><tbody><tr><td>
+                  C++
+                </td><td>
+                  M4 onward
+                </td></tr><tr><td>
+                  Java
+                </td><td>
+                  M5 anticipated
+                </td></tr></tbody></table></div></div><br class="table-break"><p>
+            Contents
+          </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
+                <a class="xref" href="ch01s09.html#ACL-v2ACLfileformatforbrokers" title="1.9.1.  v2 ACL file format for brokers">Section 1.9.1, &#8220;
+      v2 ACL file format for brokers
+    &#8221;</a>
+              </p></li><li class="listitem"><p>
+                </p><div class="itemizedlist"><ul class="itemizedlist" type="circle"><li class="listitem"><p>
+                    <a class="xref" href="ch01s09.html#ACL-Specification" title="1.9.1.1.  Specification">Section 1.9.1.1, &#8220;
+            Specification
+          &#8221;</a>
+                  </p></li><li class="listitem"><p>
+                    <a class="xref" href="ch01s09.html#ACL-Validation" title="1.9.1.2.  Validation">Section 1.9.1.2, &#8220;
+            Validation
+          &#8221;</a>
+                  </p></li><li class="listitem"><p>
+                    <a class="xref" href="ch01s09.html#ACL-Examplefile-3A" title="1.9.1.3.  Example file:">Section 1.9.1.3, &#8220;
+            Example file:
+          &#8221;</a>
+                  </p></li></ul></div><p>
+              </p></li><li class="listitem"><p>
+                <a class="xref" href="ch01s09.html#ACL-DesignDocumentation" title="1.9.2.  Design Documentation">Section 1.9.2, &#8220;
+            Design Documentation
+          &#8221;</a>
+              </p></li><li class="listitem"><p>
+                </p><div class="itemizedlist"><ul class="itemizedlist" type="circle"><li class="listitem"><p>
+                    <a class="xref" href="ch01s09.html#ACL-MappingofACLtrapstoactionandtype" title="1.9.2.1.  Mapping of ACL traps to action and type">Section 1.9.2.1, &#8220;
+            Mapping of ACL
+            traps to action and type
+          &#8221;</a>
+                  </p></li></ul></div><p>
+              </p></li><li class="listitem"><p>
+                <a class="xref" href="ch01s09.html#ACL-v2ACLUserGuide" title="1.9.3.  v2 ACL User Guide">Section 1.9.3, &#8220;
+            v2 ACL User Guide
+          &#8221;</a>
+              </p></li><li class="listitem"><p>
+                </p><div class="itemizedlist"><ul class="itemizedlist" type="circle"><li class="listitem"><p>
+                    <a class="xref" href="ch01s09.html#ACL-WritingGood-2FFastACL" title="1.9.3.1.  Writing Good/Fast ACL">Section 1.9.3.1, &#8220;
+            Writing Good/Fast ACL
+          &#8221;</a>
+                  </p></li><li class="listitem"><p>
+                    <a class="xref" href="ch01s09.html#ACL-GettingACLtoLog" title="1.9.3.2.  Getting ACL to Log">Section 1.9.3.2, &#8220;
+            Getting ACL to Log
+          &#8221;</a>
+                  </p></li><li class="listitem"><p>
+                    <a class="xref" href="ch01s09.html#ACL-UserId-2FdomainsrunningwithCbroker" title="1.9.3.3.  User Id / domains running with C++ broker">Section 1.9.3.3, &#8220;
+            User Id /
+            domains running with C++ broker
+          &#8221;</a>
+                  </p></li></ul></div><p>
+              </p></li></ul></div><p>
+            
+          </p><div class="section" title="1.9.1.1.  Specification"><div class="titlepage"><div><div><h4 class="title"><a name="ACL-Specification"></a>1.9.1.1. 
+            Specification
+          </h4></div></div></div><p>
+             Notes on file formats
+          </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>A line starting with the character '#' will be considered a
+            comment, and are ignored.
+            </p></li><li class="listitem"><p>Since the '#' char (and others that are commonly used for
+            comments) are commonly found in routing keys and other AMQP
+            literals, it is simpler (for now) to hold off on allowing
+            trailing comments (ie comments in which everything following a
+            '#' is considered a comment). This could be reviewed later once
+            the rest of the format is finalized.
+            </p></li><li class="listitem"><p>Empty lines ("") and lines that contain only whitespace (any
+            combination of ' ', '\f', '\n', '\r', '\t', '\v') are ignored.
+            </p></li><li class="listitem"><p>All tokens are case sensitive. "name1" != "Name1" and
+            "create" != "CREATE".
+            </p></li><li class="listitem"><p>Group lists may be extended to the following line by
+            terminating the line with the '\' character. However, this may
+            only occur after the group name or any of the names following the
+            group name. Empty extension lines (ie just a '\' character) are
+            not permitted.
+              
+                </p><pre class="programlisting">
+# Examples of extending group lists using a trailing '\' character
+
+group group1 name1 name2 \
+             name3 name4 \
+             name5
+
+group group2 \
+             group1 \
+             name6
+
+# The following are illegal:
+
+# '\' must be after group name
+group \
+      group3 name7 name8
+
+# No empty extension lines
+group group4 name9 \
+                   \
+             name10
+</pre><p>
+              
+            </p></li><li class="listitem"><p>Additional whitespace (ie more than one whitespace char)
+            between and after tokens is ignored. However group and acl
+            definitions must start with "group" or "acl" respectively and
+            with no preceding whitespace.
+            </p></li><li class="listitem"><p>All acl rules are limited to a single line.
+            </p></li><li class="listitem"><p>Rules are interpreted from the top of the file down until the
+            name match is obtained; at which point processing stops.
+            </p></li><li class="listitem"><p>The keyword "all" is reserved, and matches all individuals,
+            groups and actions. It may be used in place of a group or
+            individual name and/or an action - eg "acl allow all all", "acl
+            deny all all" or "acl deny user1 all".
+            </p></li><li class="listitem"><p>The last line of the file (whether present or not) will be
+            assumed to be "acl deny all all". If present in the file, any
+            lines below this one are ignored.
+            </p></li><li class="listitem"><p>Names and group names may contain only a-z, A-Z, 0-9,
+            '-','_'.
+            </p></li><li class="listitem"><p>Rules must be preceded by any group definitions they may use;
+            any name not previously defined as a group will be assumed to be
+            that of an individual.
+            </p></li><li class="listitem"><p>ACL rules must have the following tokens in order on a single
+            line:
+              </p><div class="itemizedlist"><ul class="itemizedlist" type="circle"><li class="listitem"><p>The string literal "acl";
+                </p></li><li class="listitem"><p>The permission;
+                </p></li><li class="listitem"><p>The name of a single group or individual or the keyword
+                "all";
+                </p></li><li class="listitem"><p>The name of an action or the keyword "all";
+                </p></li><li class="listitem"><p>Optionally, a single object name or the keyword "all";
+                </p></li><li class="listitem"><p>If the object is present, then optionally one or more
+                property name-value pair(s) (in the form property=value).
+                </p></li></ul></div><p>
+            </p></li></ul></div><pre class="programlisting">
+user = username[@domain[/realm]]
+user-list = user1 user2 user3 ...
+group-name-list = group1 group2 group3 ...
+
+group &lt;group-name&gt; = [user-list] [group-name-list]
+
+
+permission = [allow|allow-log|deny|deny-log]
+action = [consume|publish|create|access|bind|unbind|delete|purge|update]
+object = [virtualhost|queue|exchange|broker|link|route|method]
+property = [name|durable|owner|routingkey|passive|autodelete|exclusive|type|alternate|queuename|schemapackage|schemaclass]
+
+acl permission {&lt;group-name&gt;|&lt;user-name&gt;|"all"} {action|"all"} [object|"all"] [property=&lt;property-value&gt;]
+</pre></div><div class="section" title="1.9.1.2.  Validation"><div class="titlepage"><div><div><h4 class="title"><a name="ACL-Validation"></a>1.9.1.2. 
+            Validation
+          </h4></div></div></div><p>
+            The new ACL file format needs to perform validation on the acl
+            rules. The validation should be performed depending on the set
+            value:
+          </p><p>
+            strict-acl-validation=none
+            The default setting should be 'warn'
+          </p><p>
+            On validation of this acl the following checks would be expected:
+          </p><pre class="programlisting">
+acl allow client publish routingkey=exampleQueue exchange=amq.direct
+</pre><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>The If the user 'client' cannot be found, if the
+            authentication mechanism cannot be queried then a 'user' value
+            should be added to the file.
+            </p></li><li class="listitem"><p>There is an exchange called 'amq.direct'
+            </p></li><li class="listitem"><p>There is a queue bound to 'exampleQueue' on 'amq.direct'
+            </p></li></ol></div><p>
+            Each of these checks that fail will result in a log statement
+            being generated.
+          </p><p>
+            In the case of a fatal logging the full file will be validated
+            before the broker shuts down.
+          </p></div><div class="section" title="1.9.1.3.  Example file:"><div class="titlepage"><div><div><h4 class="title"><a name="ACL-Examplefile-3A"></a>1.9.1.3. 
+            Example file:
+          </h4></div></div></div><pre class="programlisting">
+
+# Some groups
+group admin ted@QPID martin@QPID
+group user-consume martin@QPID ted@QPID
+group group2 kim@QPID user-consume rob@QPID
+group publisher group2 \
+                tom@QPID andrew@QPID debbie@QPID
+
+# Some rules
+acl allow carlt@QPID create exchange name=carl.*
+acl deny rob@QPID create queue
+acl allow guest@QPID bind exchange name=amq.topic routingkey=stocks.ibm.#  owner=self
+acl allow user-consume create queue name=tmp.*
+
+acl allow publisher publish all durable=false
+acl allow publisher create queue name=RequestQueue
+acl allow consumer consume queue durable=true
+acl allow fred@QPID create all
+acl allow bob@QPID all queue
+acl allow admin all
+acl deny kim@QPID all
+acl allow all consume queue owner=self
+acl allow all bind exchange owner=self
+
+# Last (default) rule
+acl deny all all
+</pre></div></div><div class="section" title="1.9.2.  Design Documentation"><div class="titlepage"><div><div><h3 class="title"><a name="ACL-DesignDocumentation"></a>1.9.2. 
+            Design Documentation
+          </h3></div></div></div><div class="section" title="1.9.2.1.  Mapping of ACL traps to action and type"><div class="titlepage"><div><div><h4 class="title"><a name="ACL-MappingofACLtrapstoactionandtype"></a>1.9.2.1. 
+            Mapping of ACL
+            traps to action and type
+          </h4></div></div></div><p>
+            The C++ broker maps the ACL traps in the follow way for AMQP
+            0-10:
+            The Java broker currently only performs ACLs on the AMQP
+            connection not on management functions:
+          </p><div class="table"><a name="id2653684"></a><p class="title"><b>Table 1.5. Mapping ACL Traps</b></p><div class="table-contents"><table summary="Mapping ACL Traps" border="1"><colgroup><col><col><col><col><col></colgroup><thead><tr><th>
+                  Object
+                </th><th>
+                  Action
+                </th><th>
+                  Properties
+                </th><th>
+                  Trap C++
+                </th><th>
+                  Trap Java
+                </th></tr></thead><tbody><tr><td>
+                  Exchange
+                </td><td>
+                  Create
+                </td><td>
+                  name type alternate passive durable
+                </td><td>
+                  ExchangeHandlerImpl::declare
+                </td><td>
+                  ExchangeDeclareHandler
+                </td></tr><tr><td>
+                  Exchange
+                </td><td>
+                  Delete
+                </td><td>
+                  name
+                </td><td>
+                  ExchangeHandlerImpl::delete
+                </td><td>
+                  ExchangeDeleteHandler
+                </td></tr><tr><td>
+                  Exchange
+                </td><td>
+                  Access
+                </td><td>
+                  name
+                </td><td>
+                  ExchangeHandlerImpl::query
+                </td><td>
+
+                </td></tr><tr><td>
+                  Exchange
+                </td><td>
+                  Bind
+                </td><td>
+                  name routingkey queuename owner
+                </td><td>
+                  ExchangeHandlerImpl::bind
+                </td><td>
+                  QueueBindHandler
+                </td></tr><tr><td>
+                  Exchange
+                </td><td>
+                  Unbind
+                </td><td>
+                  name routingkey
+                </td><td>
+                  ExchangeHandlerImpl::unbind
+                </td><td>
+                  ExchangeUnbindHandler
+                </td></tr><tr><td>
+                  Exchange
+                </td><td>
+                  Access
+                </td><td>
+                  name queuename routingkey
+                </td><td>
+                  ExchangeHandlerImpl::bound
+                </td><td>
+                  
+                </td></tr><tr><td>
+                  Exchange
+                </td><td>
+                  Publish
+                </td><td>
+                  name routingKey
+                </td><td>
+                  SemanticState::route
+                </td><td>
+                  BasicPublishMethodHandler
+                </td></tr><tr><td>
+                  Queue
+                </td><td>
+                  Access
+                </td><td>
+                  name
+                </td><td>
+                  QueueHandlerImpl::query
+                </td><td>
+                  
+                </td></tr><tr><td>
+                  Queue
+                </td><td>
+                  Create
+                </td><td>
+                  name alternate passive durable exclusive autodelete
+                </td><td>
+                  QueueHandlerImpl::declare
+                </td><td>
+                  QueueDeclareHandler
+                </td></tr><tr><td>
+                  Queue
+                </td><td>
+                  Purge
+                </td><td>
+                  name
+                </td><td>
+                  QueueHandlerImpl::purge
+                </td><td>
+                  QueuePurgeHandler
+                </td></tr><tr><td>
+                  Queue
+                </td><td>
+                  Purge
+                </td><td>
+                  name
+                </td><td>
+                  Management::Queue::purge
+                </td><td>
+                  
+                </td></tr><tr><td>
+                  Queue
+                </td><td>
+                  Delete
+                </td><td>
+                  name
+                </td><td>
+                  QueueHandlerImpl::delete
+                </td><td>
+                  QueueDeleteHandler
+                </td></tr><tr><td>
+                  Queue
+                </td><td>
+                  Consume
+                </td><td>
+                  name (possibly add in future?)
+                </td><td>
+                  MessageHandlerImpl::subscribe
+                </td><td>
+                  BasicConsumeMethodHandler
+                  BasicGetMethodHandler
+                </td></tr><tr><td>
+                  &lt;Object&gt;
+                </td><td>
+                  Update
+                </td><td>
+                   
+                </td><td>
+                  ManagementProperty::set
+                </td><td>
+                  
+                </td></tr><tr><td>
+                  &lt;Object&gt;
+                </td><td>
+                  Access
+                </td><td>
+                   
+                </td><td>
+                  ManagementProperty::read
+                </td><td>
+                  
+                </td></tr><tr><td>
+                  Link
+                </td><td>
+                  Create
+                </td><td>
+                   
+                </td><td>
+                  Management::connect
+                </td><td>
+                  
+                </td></tr><tr><td>
+                  Route
+                </td><td>
+                  Create
+                </td><td>
+                   
+                </td><td>
+                  Management:: -createFederationRoute-
+                </td><td>
+                  
+                </td></tr><tr><td>
+                  Route
+                </td><td>
+                  Delete
+                </td><td>
+                   
+                </td><td>
+                  Management:: -deleteFederationRoute-
+                </td><td>
+                  
+                </td></tr><tr><td>
+                  Virtualhost
+                </td><td>
+                  Access
+                </td><td>
+                  name
+                </td><td>
+                  TBD
+                </td><td>
+                  ConnectionOpenMethodHandler
+                </td></tr></tbody></table></div></div><br class="table-break"><p>
+            Management actions that are not explicitly given a name property
+            it will default the name property to management method name, if
+            the action is 'W' Action will be 'Update', if 'R' Action will be
+            'Access'.
+          </p><p>
+            for example, if the mgnt method 'joinCluster' was not mapped in
+            schema it will be mapped in ACL file as follows
+          </p><div class="table"><a name="id2655978"></a><p class="title"><b>Table 1.6. Mapping Management Actions to ACL</b></p><div class="table-contents"><table summary="Mapping Management Actions to ACL" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>
+                  Object
+                </th><th>
+                  Action
+                </th><th>
+                  Property
+                </th></tr></thead><tbody><tr><td>
+                  Broker
+                </td><td>
+                  Update
+                </td><td>
+                  name=joinCluster
+                </td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="section" title="1.9.3.  v2 ACL User Guide"><div class="titlepage"><div><div><h3 class="title"><a name="ACL-v2ACLUserGuide"></a>1.9.3. 
+            v2 ACL User Guide
+          </h3></div></div></div><div class="section" title="1.9.3.1.  Writing Good/Fast ACL"><div class="titlepage"><div><div><h4 class="title"><a name="ACL-WritingGood-2FFastACL"></a>1.9.3.1. 
+            Writing Good/Fast ACL
+          </h4></div></div></div><p>
+            The file gets read top down and rule get passed based on the
+            first match. In the following example the first rule is a dead
+            rule. I.e. the second rule is wider than the first rule. DON'T do
+            this, it will force extra analysis, worst case if the parser does
+            not kill the dead rule you might get a false deny.
+          </p><pre class="programlisting">
+allow peter@QPID create queue name=tmp &lt;-- dead rule!!
+allow peter@QPID create queue
+deny all all
+</pre><p>
+            By default files end with
+          </p><pre class="programlisting">
+deny all all
+</pre><p>
+            the mode of the ACL engine can be swapped to be allow based by
+            putting the following at the end of the file
+          </p><pre class="programlisting">
+allow all all
+</pre><p>
+            Note that 'allow' based file will be a LOT faster for message
+            transfer. This is because the AMQP specification does not allow
+            for creating subscribes on publish, so the ACL is executed on
+            every message transfer. Also, ACL's rules using less properties
+            on publish will in general be faster.
+          </p></div><div class="section" title="1.9.3.2.  Getting ACL to Log"><div class="titlepage"><div><div><h4 class="title"><a name="ACL-GettingACLtoLog"></a>1.9.3.2. 
+            Getting ACL to Log
+          </h4></div></div></div><p>
+            In order to get log messages from ACL actions use allow-log and
+            deny-log for example
+          </p><pre class="programlisting">
+allow-log john@QPID all all
+deny-log guest@QPID all all
+</pre></div><div class="section" title="1.9.3.3.  User Id / domains running with C++ broker"><div class="titlepage"><div><div><h4 class="title"><a name="ACL-UserId-2FdomainsrunningwithCbroker"></a>1.9.3.3. 
+            User Id /
+            domains running with C++ broker
+          </h4></div></div></div><p>
+            The user-id used for ACL is taken from the connection user-id.
+            Thus in order to use ACL the broker authentication has to be
+            setup. i.e. (if --auth no is used in combination with ACL the
+            broker will deny everything)
+          </p><p>
+            The user id in the ACL file is of the form
+            &lt;user-id&gt;@&lt;domain&gt; The Domain is configured via the
+            SASL configuration for the broker, and the domain/realm for qpidd
+            is set using --realm and default to 'QPID'.
+          </p><p>
+            To load the ACL module use, load the acl module cmd line or via
+            the config file
+          </p><pre class="programlisting">
+./src/qpidd --load-module src/.libs/acl.so
+</pre><p>
+            The ACL plugin provides the following option '--acl-file'. If do
+            ACL file is supplied the broker will not enforce ACL. If an ACL
+            file name is supplied, and the file does not exist or is invalid
+            the broker will not start.
+          </p><pre class="programlisting">
+ACL Options:
+  --acl-file FILE       The policy file to load from, loaded from data dir
+</pre></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch01s08.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="ch01s10.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">1.8. High Availability Messaging Clusters </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 1.10. 
+      AMQP compatibility
+    </td></tr></table></div></body></html>

Added: qpid/site/docs/books/0.8/AMQP-Messaging-Broker-CPP-Book/html/ch01s10.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/0.8/AMQP-Messaging-Broker-CPP-Book/html/ch01s10.html?rev=1042462&view=auto
==============================================================================
--- qpid/site/docs/books/0.8/AMQP-Messaging-Broker-CPP-Book/html/ch01s10.html (added)
+++ qpid/site/docs/books/0.8/AMQP-Messaging-Broker-CPP-Book/html/ch01s10.html Sun Dec  5 21:59:22 2010
@@ -0,0 +1,393 @@
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>1.10.  AMQP compatibility</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" 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="ch01s09.html" title="1.9.  ACL"><link rel="next" href="ch01s11.html" title="1.11. Qpid Interoperability Documentation"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.10. 
+      AMQP compatibility
+    </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01s09.html">Prev</a> </td><th width="60%" align="center">Chapter 1.             
+      Running the AMQP Messaging Broker
+    </th><td width="20%" align="right"> <a accesskey="n" href="ch01s11.html">Next</a></td></tr></table><hr></div><div class="section" title="1.10.  AMQP compatibility"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="AMQP-Compatibility"></a>1.10. 
+      AMQP compatibility
+    </h2></div></div></div><p>
+            Qpid provides the most complete and compatible implementation
+            of AMQP. And is the most aggressive in implementing the latest
+            version of the specification.
+          </p><p>
+            There are two brokers:
+          </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>C++ with support for AMQP 0-10</p></li><li class="listitem"><p>Java with support for AMQP 0-8 and 0-9 (0-10 planned)</p></li></ul></div><p>
+            There are client libraries for C++, Java (JMS), .Net (written in
+            C#), python and ruby.
+          </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>All clients support 0-10 and interoperate with the C++
+            broker.
+            </p></li></ul></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>The JMS client supports 0-8, 0-9 and 0-10 and interoperates
+            with both brokers.
+            </p></li></ul></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>The python and ruby clients will also support all versions,
+            but the API is dynamically driven by the specification used and
+            so differs between versions. To work with the Java broker you
+            must use 0-8 or 0-9, to work with the C++ broker you must use
+            0-10.
+            </p></li></ul></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>There are two separate C# clients, one for 0-8 that
+            interoperates with the Java broker, one for 0-10 that
+            inteoperates with the C++ broker.
+            </p></li></ul></div><p>
+            QMF Management is supported in Ruby, Python, C++, and via QMan
+            for Java JMX &amp; WS-DM.
+          </p><div class="section" title="1.10.1.  AMQP Compatibility of Qpid releases:"><div class="titlepage"><div><div><h3 class="title"><a name="AMQPcompatibility-AMQPCompatibilityofQpidreleases-3A"></a>1.10.1. 
+            AMQP
+            Compatibility of Qpid releases:
+          </h3></div></div></div><p>
+            Qpid implements the AMQP Specification, and as the specification
+            has progressed Qpid is keeping up with the updates. This means
+            that different Qpid versions support different versions of AMQP.
+            Here is a simple guide on what use.
+          </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="id2654992"></a><p class="title"><b>Table 1.7. 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
+                </td><td>
+                   
+                </td><td>
+                   
+                </td><td>
+                   
+                </td><td>
+                   
+                </td></tr><tr><td>
+                   
+                </td><td>
+                   
+                </td><td>
+                  M2.1
+                </td><td>
+                  M3
+                </td><td>
+                  M4
+                </td><td>
+                  0.5
+                </td></tr><tr><td>
+                  java client
+                </td><td>
+                  0-10
+                </td><td>
+                   
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td></tr><tr><td>
+                   
+                </td><td>
+                  0-9
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td></tr><tr><td>
+                   
+                </td><td>
+                  0-8
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td></tr><tr><td>
+                  java broker
+                </td><td>
+                  0-10
+                </td><td>
+                   
+                </td><td>
+                   
+                </td><td>
+                   
+                </td><td>
+                  P
+                </td></tr><tr><td>
+                   
+                </td><td>
+                  0-9
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td></tr><tr><td>
+                   
+                </td><td>
+                  0-8
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td></tr><tr><td>
+                  c++ client/broker
+                </td><td>
+                  0-10
+                </td><td>
+                   
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td></tr><tr><td>
+                   
+                </td><td>
+                  0-9
+                </td><td>
+                  Y
+                </td><td>
+                   
+                </td><td>
+                   
+                </td><td>
+                   
+                </td></tr><tr><td>
+                  python client
+                </td><td>
+                  0-10
+                </td><td>
+                   
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td></tr><tr><td>
+                   
+                </td><td>
+                  0-9
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td></tr><tr><td>
+                   
+                </td><td>
+                  0-8
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td></tr><tr><td>
+                  ruby client
+                </td><td>
+                  0-10
+                </td><td>
+                   
+                </td><td>
+                   
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td></tr><tr><td>
+                   
+                </td><td>
+                  0-8
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td></tr><tr><td>
+                  C# client
+                </td><td>
+                  0-10
+                </td><td>
+                   
+                </td><td>
+                   
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td></tr><tr><td>
+                   
+                </td><td>
+                  0-8
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td></tr></tbody></table></div></div><br class="table-break"></div><div class="section" title="1.10.2.  Interop table by AMQP specification version"><div class="titlepage"><div><div><h3 class="title"><a name="AMQPcompatibility-InteroptablebyAMQPspecificationversion"></a>1.10.2. 
+            Interop
+            table by AMQP specification version
+          </h3></div></div></div><p>
+            Above table represented in another format.
+          </p><div class="table"><a name="id2656743"></a><p class="title"><b>Table 1.8. 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
+                </td><td>
+                  0-8
+                </td><td>
+                  0-9
+                </td><td>
+                  0-10
+                </td></tr><tr><td>
+                  java client
+                </td><td>
+                  M3 M4 0.5
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td></tr><tr><td>
+                  java client
+                </td><td>
+                  M2.1
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  N
+                </td></tr><tr><td>
+                  java broker
+                </td><td>
+                  M3 M4 0.5
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  N
+                </td></tr><tr><td>
+                  java broker
+                </td><td>
+                  trunk
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  P
+                </td></tr><tr><td>
+                  java broker
+                </td><td>
+                  M2.1
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  N
+                </td></tr><tr><td>
+                  c++ client/broker
+                </td><td>
+                  M3 M4 0.5
+                </td><td>
+                  N
+                </td><td>
+                  N
+                </td><td>
+                  Y
+                </td></tr><tr><td>
+                  c++ client/broker
+                </td><td>
+                  M2.1
+                </td><td>
+                  N
+                </td><td>
+                  Y
+                </td><td>
+                  N
+                </td></tr><tr><td>
+                  python client
+                </td><td>
+                  M3 M4 0.5
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td></tr><tr><td>
+                  python client
+                </td><td>
+                  M2.1
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  N
+                </td></tr><tr><td>
+                  ruby client
+                </td><td>
+                  M3 M4 0.5
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  N
+                </td></tr><tr><td>
+                  ruby client
+                </td><td>
+                  trunk
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  P
+                </td></tr><tr><td>
+                  C# client
+                </td><td>
+                  M3 M4 0.5
+                </td><td>
+                  Y
+                </td><td>
+                  N
+                </td><td>
+                  N
+                </td></tr><tr><td>
+                  C# client
+                </td><td>
+                  trunk
+                </td><td>
+                  Y
+                </td><td>
+                  N
+                </td><td>
+                  Y
+                </td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch01s09.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="ch01s11.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">1.9. 
+      ACL
+   </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 1.11. Qpid Interoperability Documentation</td></tr></table></div></body></html>

Added: qpid/site/docs/books/0.8/AMQP-Messaging-Broker-CPP-Book/html/ch01s11.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/0.8/AMQP-Messaging-Broker-CPP-Book/html/ch01s11.html?rev=1042462&view=auto
==============================================================================
--- qpid/site/docs/books/0.8/AMQP-Messaging-Broker-CPP-Book/html/ch01s11.html (added)
+++ qpid/site/docs/books/0.8/AMQP-Messaging-Broker-CPP-Book/html/ch01s11.html Sun Dec  5 21:59:22 2010
@@ -0,0 +1,232 @@
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>1.11. Qpid Interoperability Documentation</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" 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="ch01s10.html" title="1.10.  AMQP compatibility"><link rel="next" href="ch02.html" title="Chapter 2.  Managing the AMQP Messaging Broker"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.11. Qpid Interoperability Documentation</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01s10.html">Prev</a> </td><th width="60%" align="center">Chapter 1.             
+      Running the AMQP Messaging Broker
+    </th><td width="20%" align="right"> <a accesskey="n" href="ch02.html">Next</a></td></tr></table><hr></div><div class="section" title="1.11. Qpid Interoperability Documentation"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="QpidInteroperabilityDocumentation-QpidInteroperabilityDocumentation"></a>1.11. Qpid Interoperability Documentation</h2></div></div></div><p>
+            This page documents the various interoperable features of the
+            Qpid clients.
+          </p><div class="section" title="1.11.1.  SASL"><div class="titlepage"><div><div><h3 class="title"><a name="QpidInteroperabilityDocumentation-SASL"></a>1.11.1. 
+            SASL
+          </h3></div></div></div><p>
+            
+          </p><div class="section" title="1.11.1.1.  Standard Mechanisms"><div class="titlepage"><div><div><h4 class="title"><a name="QpidInteroperabilityDocumentation-StandardMechanisms"></a>1.11.1.1. 
+            Standard
+            Mechanisms
+          </h4></div></div></div><p>
+            <a class="ulink" href="http://en.wikipedia.org/wiki/Simple_Authentication_and_Security_Layer#SASL_mechanisms" target="_top">http://en.wikipedia.org/wiki/Simple_Authentication_and_Security_Layer#SASL_mechanisms</a>
+          </p><p>
+            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="id2656531"></a><p class="title"><b>Table 1.9. 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
+                </td><td>
+                  CRAM-MD5
+                </td><td>
+                  DIGEST-MD5
+                </td><td>
+                  EXTERNAL
+                </td><td>
+                  GSSAPI/Kerberos
+                </td><td>
+                  PLAIN
+                </td></tr><tr><td>
+                  C++ Broker
+                </td><td>
+                  M3[<a class="xref" href="ch01s11.html#QpidInteroperabilityDocumentation-1">Section 1.11.1.1, &#8220;
+            Standard
+            Mechanisms
+          &#8221;</a>]
+                </td><td>
+                  M3[<a class="xref" href="ch01s11.html#QpidInteroperabilityDocumentation-1">Section 1.11.1.1, &#8220;
+            Standard
+            Mechanisms
+          &#8221;</a>,<a class="xref" href="ch01s11.html#QpidInteroperabilityDocumentation-2">Section 1.11.1.1, &#8220;
+            Standard
+            Mechanisms
+          &#8221;</a>]
+                </td><td>
+                   
+                </td><td>
+                   
+                </td><td>
+                  M3[<a class="xref" href="ch01s11.html#QpidInteroperabilityDocumentation-1">Section 1.11.1.1, &#8220;
+            Standard
+            Mechanisms
+          &#8221;</a>,<a class="xref" href="ch01s11.html#QpidInteroperabilityDocumentation-2">Section 1.11.1.1, &#8220;
+            Standard
+            Mechanisms
+          &#8221;</a>]
+                </td><td>
+                  M1
+                </td></tr><tr><td>
+                  C++ Client
+                </td><td>
+                  M3[<a class="xref" href="ch01s11.html#QpidInteroperabilityDocumentation-1">Section 1.11.1.1, &#8220;
+            Standard
+            Mechanisms
+          &#8221;</a>]
+                </td><td>
+                   
+                </td><td>
+                   
+                </td><td>
+                   
+                </td><td>
+                   
+                </td><td>
+                  M1
+                </td></tr><tr><td>
+                  Java Broker
+                </td><td>
+                   
+                </td><td>
+                  M1
+                </td><td>
+                   
+                </td><td>
+                   
+                </td><td>
+                   
+                </td><td>
+                  M1
+                </td></tr><tr><td>
+                  Java Client
+                </td><td>
+                   
+                </td><td>
+                  M1
+                </td><td>
+                   
+                </td><td>
+                   
+                </td><td>
+                   
+                </td><td>
+                  M1
+                </td></tr><tr><td>
+                  .Net Client
+                </td><td>
+                  M2
+                </td><td>
+                  M2
+                </td><td>
+                  M2
+                </td><td>
+                  M2
+                </td><td>
+                   
+                </td><td>
+                  M2
+                </td></tr><tr><td>
+                  Python Client
+                </td><td>
+                   
+                </td><td>
+                   
+                </td><td>
+                   
+                </td><td>
+                   
+                </td><td>
+                   
+                </td><td>
+                  ?
+                </td></tr><tr><td>
+                  Ruby Client
+                </td><td>
+                   
+                </td><td>
+                   
+                </td><td>
+                   
+                </td><td>
+                   
+                </td><td>
+                   
+                </td><td>
+                  ?
+                </td></tr></tbody></table></div></div><br class="table-break"><p><a name="QpidInteroperabilityDocumentation-1"></a>        
+            1: Support for these will be in M3 (currently available on
+            trunk).
+	  </p><p><a name="QpidInteroperabilityDocumentation-2"></a>2: C++ Broker uses <a class="ulink" href="http://freshmeat.net/projects/cyrussasl/" target="_top">Cyrus SASL</a> which
+            supports CRAM-MD5 and GSSAPI but these have not been tested yet
+          </p></div><div class="section" title="1.11.1.2.  Custom Mechanisms"><div class="titlepage"><div><div><h4 class="title"><a name="QpidInteroperabilityDocumentation-CustomMechanisms"></a>1.11.1.2. 
+            Custom
+            Mechanisms
+          </h4></div></div></div><p>
+            There have been some custom mechanisms added to our
+            implementations.
+          </p><div class="table"><a name="id2657136"></a><p class="title"><b>Table 1.10. 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
+                </td><td>
+                  CRAM-MD5-HASHED
+                </td></tr><tr><td>
+                  C++ Broker
+                </td><td>
+                   
+                </td><td>
+                   
+                </td></tr><tr><td>
+                  C++ Client
+                </td><td>
+                   
+                </td><td>
+                   
+                </td></tr><tr><td>
+                  Java Broker
+                </td><td>
+                  M1
+                </td><td>
+                  M2
+                </td></tr><tr><td>
+                  Java Client
+                </td><td>
+                  M1
+                </td><td>
+                  M2
+                </td></tr><tr><td>
+                  .Net Client
+                </td><td>
+                   
+                </td><td>
+                   
+                </td></tr><tr><td>
+                  Python Client
+                </td><td>
+                  M2
+                </td><td>
+                   
+                </td></tr><tr><td>
+                  Ruby Client
+                </td><td>
+                  M2
+                </td><td>
+                   
+                </td></tr></tbody></table></div></div><br class="table-break"><div class="section" title="1.11.1.2.1. AMQPLAIN"><div class="titlepage"><div><div><h5 class="title"><a name="id2657288"></a>1.11.1.2.1. AMQPLAIN</h5></div></div></div><p></p></div><div class="section" title="1.11.1.2.2. CRAM-MD5-HASHED"><div class="titlepage"><div><div><h5 class="title"><a name="id2657297"></a>1.11.1.2.2. 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
+            secure either the broker must encrypt the password file or the
+            need for the password being stored must be removed.
+          </p><p>
+            The CRAM-MD5-HASHED SASL plugin removes the need for the plain
+            text password to be stored on disk. The mechanism defers all
+            functionality to the build in CRAM-MD5 module the only change is
+            on the client side where it generates the hash of the password
+            and uses that value as the password. This means that the Java
+            Broker only need store the password hash on the file system.
+            While a one way hash is not very secure compared to other forms
+            of encryption in environments where the having the password in
+            plain text is unacceptable this will provide and additional layer
+            to protect the password. In particular this offers some
+            protection where the same password may be shared amongst many
+            systems. It offers no real extra protection against attacks on
+            the broker (the secret is now the hash rather than the password).
+          </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="ch01s10.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="ch02.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">1.10. 
+      AMQP compatibility
+     </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 2.             
+      Managing the AMQP Messaging Broker
+    </td></tr></table></div></body></html>



---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:commits-subscribe@qpid.apache.org