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=1368244&r1=1368243&r2=1368244&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 Wed Aug 1 20:54:46 2012 @@ -1,6 +1,6 @@ -1.6. LVQ - Last Value Queue

1.6. LVQ - Last Value Queue

1.6.1. Understanding LVQ

+ > LVQ - Last Value Queue

1.6. LVQ - Last Value Queue

1.6.1. Understanding LVQ

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 @@ -35,7 +35,7 @@ number of messages in the queue shall not exceed the number of distinct keys in use.

-

1.6.1.1. Common Use-Cases

  • +

    1.6.1.1. Common Use-Cases

    • LVQ with zero or one consuming subscriptions - In this case, if the consumer drops momentarily or is slower than the producer(s), it will only receive current information relative to the message @@ -102,6 +102,6 @@ controlled by the qpid.last_value_queue and qpid.last_value_queue_no_browse argument values. These modes are deprecated and should not be used. -

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=1368244&r1=1368243&r2=1368244&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 Wed Aug 1 20:54:46 2012 @@ -1,6 +1,6 @@ -1.14. Queue Replication with the HA module

1.14. Queue Replication with the HA module

+ > Queue Replication with the HA module

1.14. Queue Replication with the HA module

As well as support for an active-passive cluster, the ha module also allows you to replicate individual queues. The original queue is used as normal. The replica queue is updated @@ -25,6 +25,6 @@

       qpid-ha replicate -b node2 node1 myqueue
     

-

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=1368244&r1=1368243&r2=1368244&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 Wed Aug 1 20:54:46 2012 @@ -1,10 +1,10 @@ -2.2.  Qpid Management Framework

2.2.  + > + Qpid Management Framework +

2.2.  Qpid Management Framework -

  • +

  • Section 2.2.1, “ What Is QMF ” @@ -18,7 +18,7 @@ QMF Concepts ”

  • -

    • +

      • Section 2.2.3.1, “ Console, Agent, and Broker @@ -193,7 +193,7 @@

        The XML syntax for <property> and <statistic> have the following XML-attributes: -

        Table 2.1. XML Attributes for QMF Properties and Statistics

        +

        Table 2.1. XML Attributes for QMF Properties and Statistics

        Attribute <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: -

        Table 2.2. QMF Datatypes

        +

        Table 2.2. QMF Datatypes

        QMF Type 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. -

        Table 2.3. XML Schema Mapping for QMF Types

        +

        Table 2.3. XML Schema Mapping for QMF Types

        XML Type QMF Type @@ -579,8 +579,8 @@

        2.2.6.  How to Write a QMF Agent -

        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=1368244&r1=1368243&r2=1368244&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 Wed Aug 1 20:54:46 2012 @@ -1,10 +1,10 @@ -2.3.  QMF Python Console Tutorial

        2.3.  + > + QMF Python Console Tutorial +

        2.3.  QMF Python Console Tutorial -

        • +

        • Section 2.3.1, “ Prerequisite - Install Qpid Messaging @@ -15,7 +15,7 @@ Console Operations ”

        • -

          • +

            • Section 2.3.2.1, “ Creating a QMF Console Session and Attaching to a Broker ” @@ -25,7 +25,7 @@ Managed Objects ”

            • -

              • +

                • the section called “ Viewing Properties and Statistics of an Object ” @@ -42,7 +42,7 @@ Console Operations ”

                • -

                  • +

                    • Section 2.3.3.1, “ Creating a Console Class to Receive Asynchronous Data ” @@ -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. -

                      Table 2.4. QMF Python Console Class Methods

                      +

                      Table 2.4. QMF Python Console Class Methods

                      Method Arguments @@ -641,7 +641,7 @@ sess.delBroker(broker) After reporting the statistics, it checks the timestamps of the proxy. getTimestamps returns a list of timestamps in the order: -

                      • +

                        • Current - The timestamp of the sending of this update.

                        • Create - The time of the object's creation @@ -699,6 +699,6 @@ sess.bindClass("org.apache.qpid.broker", Make sure your code is written to handle this possibility.

                      2.3.4.  Discovering what Kinds of Objects are Available -

                      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=1368244&r1=1368243&r2=1368244&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 Wed Aug 1 20:54:46 2012 @@ -1,6 +1,6 @@ -1.8. Active-active Messaging Clusters

                      1.8. Active-active Messaging Clusters

                      + > Active-active Messaging Clusters

                      1.8. Active-active Messaging Clusters

                      Active-active Messaging Clusters provide fault tolerance by ensuring that every broker in a cluster has the same queues, exchanges, messages, and bindings, and allowing a client to fail over to a new broker and continue without any loss of messages if the current broker fails or becomes unavailable. Active-active refers to the fact that all brokers in the cluster can actively serve clients. 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 cluster, and brokers can be added to or removed from a cluster while it is in use.

                      High Availability Messaging Clusters are implemented using using the OpenAIS Cluster Framework. @@ -38,7 +38,7 @@ 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 — 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.

                      The following settings can differ for brokers on a given cluster: -

                      • +

                        • logging options

                        • cluster-url — if set, it will be different for each broker. @@ -82,7 +82,7 @@ ssl_addr = "ssl:" host [":" port]

                          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:

                          -
                          • +

                            • amqp:tcp:192.168.1.103:5672 advertizes a single address to the broker for failover.

                            • amqp:tcp:192.168.1.103:5672,tcp:192.168.1.105:5672 advertizes two different addresses to the broker for failover, on two different network interfaces. @@ -215,7 +215,7 @@

                              The cluster can start if:

                              -

                              • +

                                • all members have empty stores, or

                                • at least one member has a clean store @@ -241,8 +241,8 @@ Now you can start the cluster, all members will be initialized from the store you marked as clean.

                                1.8.5.5. Isolated failures in a persistent cluster

                                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. -

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