Reply-To: dev@qpid.apache.org Delivered-To: mailing list commits@qpid.apache.org Received: (qmail 98193 invoked by uid 99); 6 Sep 2016 16:59:26 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Sep 2016 16:59:26 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 0C0B5E0BD9; Tue, 6 Sep 2016 16:59:26 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: jross@apache.org To: commits@qpid.apache.org Date: Tue, 06 Sep 2016 17:00:06 -0000 Message-Id: <7af290d30a4942ed8353c76988ac4d70@git.apache.org> In-Reply-To: <8402d218d9cc469cba10ae715da937a5@git.apache.org> References: <8402d218d9cc469cba10ae715da937a5@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: [43/51] [partial] qpid-site git commit: QPID-7353: Update for the Qpid C++ 1.35.0 release archived-at: Tue, 06 Sep 2016 16:59:33 -0000 http://git-wip-us.apache.org/repos/asf/qpid-site/blob/eff0fe55/content/releases/qpid-cpp-1.35.0/cpp-broker/book/index.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-cpp-1.35.0/cpp-broker/book/index.html b/content/releases/qpid-cpp-1.35.0/cpp-broker/book/index.html new file mode 100644 index 0000000..7297dbe --- /dev/null +++ b/content/releases/qpid-cpp-1.35.0/cpp-broker/book/index.html @@ -0,0 +1,251 @@ + + + + + AMQP Messaging Broker (Implemented in C++) - Apache Qpid™ + + + + + + + + + + + + + +

+ + +

+ + + + + +

+ + +

AMQP Messaging Broker (Implemented in C++)
		Next

AMQP Messaging Broker (Implemented in C++)

Table of Contents

Introduction

1. + Running the AMQP Messaging Broker +

1.1. + Running a Qpid C++ Broker +

1.1.1. + Building the + C++ Broker and Client Libraries +
1.1.2. + Running the C++ Broker +
1.1.3. + Most + common questions getting qpidd running +
1.1.4. + Authentication +
1.1.5. + Slightly more + complex configuration +
1.1.6. + Loading extra modules +
1.1.7. Timestamping Received Messages
1.1.8. Logging Options

1.2. + Cheat Sheet for configuring Queue Options +

1.2.1. + Configuring + Queue Options +

1.3. + Cheat Sheet for configuring Exchange Options +

1.3.1. + Configuring Exchange Options +

1.4. Broker Federation

1.4.1. Message Routes
1.4.2. Federation Topologies
1.4.3. Federation among High Availability Message Clusters
1.4.4. The qpid-route Utility
1.4.5. Broker options affecting federation

1.5. Security

1.5.1. User Authentication
1.5.2. Authorization
1.5.3. User Connection and Queue Quotas
1.5.4. Encryption using SSL

1.6. LVQ - Last Value Queue

1.6.1. Understanding LVQ
1.6.2. Creating a Last Value Queue
1.6.3. LVQ Example
1.6.4. Deprecated LVQ Modes

1.7. + Queue State Replication +

1.7.1. + Asynchronous + Replication of Queue State +

1.8. + Producer Flow Control +

1.8.1. + Overview +
1.8.2. + User Interface +

1.9. + AMQP compatibility +

1.9.1. + AMQP + Compatibility of Qpid releases: +
1.9.2. + Interop + table by AMQP specification version +

1.10. Qpid Interoperability Documentation

1.10.1. + SASL +

1.11. + Using Message Groups +

1.11.1. + Overview +
1.11.2. + Grouping Messages +
1.11.3. + The Role of the Broker +
1.11.4. + Well Behaved Consumers +
1.11.5. + Broker Configuration +

1.12. Active-Passive Messaging Clusters

1.12.1. Overview
1.12.2. Virtual IP Addresses
1.12.3. Configuring the Brokers
1.12.4. The Cluster Resource Manager
1.12.5. Configuring with rgmanager as resource manager
1.12.6. Broker Administration Tools
1.12.7. Controlling replication of queues and exchanges
1.12.8. Client Connection and Fail-over
1.12.9. Security and Access Control.
1.12.10. Integrating with other Cluster Resource Managers
1.12.11. Using a message store in a cluster
1.12.12. Troubleshooting a cluster

1.13. Replicating Queues with the HA module

1.13.1. Replicating queues
1.13.2. Replicating queues between clusters

2. + Managing the AMQP Messaging Broker +

2.1. Managing the C++ Broker

2.1.1. + Using qpid-config +
2.1.2. + Using qpid-route +
2.1.3. + Using qpid-tool +
2.1.4. + Using + qpid-printevents +
2.1.5. Using qpid-ha

2.2. + Qpid Management Framework +

2.2.1. + What Is QMF +
2.2.2. + Getting + Started with QMF +
2.2.3. + QMF Concepts +
2.2.4. + The QMF + Protocol +
2.2.5. + How + to Write a QMF Console +
2.2.6. + How to + Write a QMF Agent +

2.3. + QMF Python Console Tutorial +

2.3.1. + Prerequisite + - Install Qpid Messaging +
2.3.2. + Synchronous + Console Operations +
2.3.3. + Asynchronous + Console Operations +
2.3.4. + Discovering what Kinds of Objects are Available +

List of Tables

1.1. QMF Management - Broker Methods for Managing the Timestamp Configuration
1.2. C++ Broker Log Severity Levels
1.3. C++ Broker Log Categories
1.4. C++ Broker Log Statement Attributes
1.5. C++ Broker Log Enable/Disable RULE Format
1.6. C++ Broker Log Enable/Disable Settings Tables
1.7. C++ Broker Log Statement Visibility Determination
1.8. QMF Management - Broker Methods for Managing the Log Enable/Disable Settings
1.9. qpid-route options
1.10. State values in $ qpid-route list connections
1.11. Broker Options for Federation
1.12. ACL Rules: permission
1.13. ACL Rules: action
1.14. ACL Rules:object
1.15. ACL Rules: property
1.16. Broker Lookup Events With Allowed Action, Object, and Properties
1.17. ACL User Name and Domain Name Substitution Keywords
1.18. Topic Exchange Wildcard Match Examples
1.19. SSL Client Environment Variables for C++ clients
1.20. Queue Declare Method Flow Control Arguments
1.21. Flow Control Statistics available in Queue's QMF Class
1.22. AMQP Version Support by Qpid Release
1.23. AMQP Version Support - alternate format
1.24. SASL Mechanism Support
1.25. SASL Custom Mechanisms
1.26. qpid-config options for creating message group queues
1.27. Queue Declare/Address Syntax Message Group Configuration Arguments
1.28. Broker Options for High Availability Messaging Cluster< /a>
1.29. HA Security Options
2.1. XML Attributes for QMF Properties and Statistics
2.2. QMF Datatypes
2.3. XML Schema Mapping for QMF Types
2.4. QMF Python Console Class Methods

List of Examples

1.1. Enabling Message Timestamping via QMF - Python
1.2. + Querying Log Settings via qpid-ctrl utility +
1.3. + Setting Log Settings via qpid-ctrl utility +
1.4. Creating a message group queue via qpid-config
1.5. Creating a message group queue using address syntax (C++)
1.6. Overriding the default message group identifier for the broker

		Next
		Introduction

+ +

+ + + +

+ Apache Qpid, Messaging built on AMQP; Copyright © 2015 + The Apache Software Foundation; Licensed under + the Apache + License, Version 2.0; Apache Qpid, Qpid, Qpid Proton, + Proton, Apache, the Apache feather logo, and the Apache Qpid + project logo are trademarks of The Apache Software + Foundation; All other marks mentioned may be trademarks or + registered trademarks of their respective owners +

+ + http://git-wip-us.apache.org/repos/asf/qpid-site/blob/eff0fe55/content/releases/qpid-cpp-1.35.0/cpp-broker/book/pr01.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-cpp-1.35.0/cpp-broker/book/pr01.html b/content/releases/qpid-cpp-1.35.0/cpp-broker/book/pr01.html new file mode 100644 index 0000000..fde0699 --- /dev/null +++ b/content/releases/qpid-cpp-1.35.0/cpp-broker/book/pr01.html @@ -0,0 +1,149 @@ + + + + + Introduction - Apache Qpid™ + + + + + + + + + + + + + +

+ + +

+ + + + + +

+ + +

Introduction
Prev		Next

Introduction

Qpid provides two AMQP messaging brokers:

Implemented in C++ - high performance, low latency, and RDMA support.
Implemented in Java - Fully JMS compliant, runs on any Java platform.

Both AMQP messaging brokers support clients in multiple + languages, as long as the messaging client and the messaging + broker use the same version of AMQP. See AMQP Compatibility to see + which messaging clients work with each broker.

This manual contains information specific to the broker that is implemented in C++.

Prev		Next
AMQP Messaging Broker (Implemented in C++)	Home	Chapter 1. + Running the AMQP Messaging Broker +

+ +

+ + + +

+ + http://git-wip-us.apache.org/repos/asf/qpid-site/blob/eff0fe55/content/releases/qpid-cpp-1.35.0/cpp-broker/book/producer-flow-control.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-cpp-1.35.0/cpp-broker/book/producer-flow-control.html b/content/releases/qpid-cpp-1.35.0/cpp-broker/book/producer-flow-control.html new file mode 100644 index 0000000..3494d99 --- /dev/null +++ b/content/releases/qpid-cpp-1.35.0/cpp-broker/book/producer-flow-control.html @@ -0,0 +1,334 @@ + + + + + producer-flow-control.html - Apache Qpid™ + + + + + + + + + + + + + +

+ + +

+ + + + + +

+ + +

1.8. + Producer Flow Control +
Prev	Chapter 1. + Running the AMQP Messaging Broker +	Next

1.8. + Producer Flow Control +

1.8.1. + Overview +

+ As of release 0.10, the C++ broker supports the use of flow control to + throttle back message producers that are at risk of overflowing a + destination queue. +

+ Each queue in the C++ broker has two threshold values associated with it: +

+ Flow Stop Threshold: this is the level of queue resource + utilization above which flow control will be enabled. Once this + threshold is crossed, the queue is considered in danger of overflow. +

+ Flow Resume Threshold - this is the level of queue resource utilization + below which flow control will be disabled. Once this threshold is + crossed, the queue is no longer considered in danger of overflow. +

+ In the above description, queue resource utilization may be + defined as the total count of messages currently enqueued, or the total + sum of all message content in bytes. +

+ The value for a queue's Flow Stop Threshold must be greater than or + equal to the value of the queue's Flow Resume Threshold. +

1.8.1.1. + Example +

+ Let's consider a queue with a maximum limit set on the total number of + messages that may be enqueued to that queue. Assume this maximum + message limit is 1000 messages. Assume also that the user configures a + Flow Stop Threshold of 900 messages, and a Flow Resume Threshold of 500 + messages. Then the following holds: +

+ The queue's initial flow control state is "OFF". +

+ While the total number of enqueued messages is less than or equal to + 900, the queue's flow control state remains "OFF". +

+ When the total number of enqueued messages is greater than 900, the + queue's flow control state transitions to "ON". +

+ When the queue's flow control state is "ON", it remains "ON" until the + total number of enqueued messages is less than 500. At that point, the queue's + flow control state transitions to "OFF". +

+ A similar example using total enqueued content bytes as the threshold + units are permitted. +

+ Thresholds may be set using both total message counts and total byte + counts. In this case, the following rules apply: +

+ 1) Flow control is "ON" when either stop threshold value is crossed. +

+ 2) Flow control remains "ON" until both resume thresholds are satisfied. +

1.8.1.2. + Example +

+ Let's consider a queue with a maximum size limit of 10K bytes, and 5000 + messages. A user may assign a Flow Stop Threshold based on a total + message count of 4000 messages. They may also assigne a Flow Stop + Threshold of 8K bytes. The queue's flow control state transitions to + "ON" if either threshold is crossed: (total-msgs greater-than 4000 OR total-bytes + greater-than 8K). +

+ Assume the user has assigned Flow Resume threshold's of 3000 messages and + 6K bytes. Then the queue's flow control will remain active until both + thresholds are satified: (total-msg less-than 3000 AND total-bytes less-than 6K). +

+ The Broker enforces flow control by delaying the completion of the + Message.Transfer command that causes a message to be delivered to a queue + with active flow control. The completion of the Message.Transfer command + is held off until flow control state transitions to "OFF" for all queues + that are a destination for that command. +

+ A message producing client is permitted to have a finite number of + commands pending completion. When the total number of these outstanding + commands reaches the limit, the client must not issue further commands + until one or more of the outstanding commands have completed. This + window of outstanding commands is considered the sender's "capacity". + This allows any given producer to have a "capacity's" worth of messages + blocked due to flow control before the sender must stop sending further + messages. +

+ This capacity window must be considered when determining a suitable + flow stop threshold for a given queue, as a producer may send its + capacity worth of messages _after_ a queue has reached the flow stop + threshold. Therefore, a flow stop threshould should be set such that + the queue can accomodate more messages without overflowing. +

+ For example, assume two clients, C1 and C2, are producing messages to + one particular destination queue. Assume client C1 has a configured + capacity of 50 messages, and client C2's capacity is 15 messages. In + this example, assume C1 and C2 are the only clients queuing messages to + a given queue. If this queue has a Flow Stop Threshold of 100 + messages, then, worst-case, the queue may receive up to 165 messages + before clients C1 and C2 are blocked from sending further messages. + This is due to the fact that the queue will enable flow control on + receipt of its 101'st message - preventing the completion of the + Message.Transfer command that carried the 101'st message. However, C1 + and C2 are allowed to have a total of 65 (50 for C1 and 15 for C2) + messages pending completion of Message.Transfer before they will stop + producing messages. Thus, up to 65 messages may be enqueued beyond the + flow stop threshold before the producers will be blocked. +

1.8.2. + User Interface +

+ By default, the C++ broker assigns a queue's flow stop and flow resume + thresholds when the queue is created. The C++ broker also allows the + user to manually specify the flow control thresholds on a per queue + basis. +

+ However, queues that have been configured with a Limit Policy of type + RING or RING-STRICT do NOT have queue flow thresholds enabled by + default. The nature of a RING queue defines its behavior when its + capacity is reach: replace the oldest message. +

+ The flow control state of a queue can be determined by the "flowState" + boolean in the queue's QMF management object. The queue's management + object also contains a counter that increments each time flow control + becomes active for the queue. +

+ The broker applies a threshold ratio to compute a queue's default flow + control configuration. These thresholds are expressed as a percentage + of a queue's maximum capacity. There is one value for determining the + stop threshold, and another for determining the resume threshold. The + user may configure these percentages using the following broker + configuration options: +

+        --default-flow-stop-threshold ("Queue capacity level at which flow control is activated.")
+        --default-flow-resume-threshold ("Queue capacity level at which flow control is de-activated.")
+

+ For example: +

+        qpidd --default-flow-stop-threshold=90 --default-flow-resume-threshold=75
+

+ Sets the default flow stop threshold to 90% of a queue's maximum + capacity and the flow resume threshold to 75% of the maximum capacity. + If a queue is created with a default-queue-limit of 10000 bytes, then + the default flow stop threshold would be 90% of 10000 = 9000 bytes and + the flow resume threshold would be 75% of 10000 = 7500. The same + computation is performed should a queue be created with a maximum size + expressed as a message count instead of a byte count. +

+ If not overridden by the user, the value of the + default-flow-stop-threshold is 80% and the value of the + default-flow-resume-threshold is 70%. +

+ The user may disable default queue flow control broker-wide by + specifying the value 0 for both of these configuration options. Note + that flow control may still be applied manually on a per-queue basis in + this case. +

+ The user may manually set the flow thresholds when creating a queue. + The following options may be provided when adding a queue using the + qpid-config command line tool: +

+        --flow-stop-size=N  Sets the queue's flow stop threshold to N total bytes.
+        --flow-resume-size=N  Sets the queue's flow resume threshold to N total bytes.
+        --flow-stop-count=N Sets the queue's flow stop threshold to N total messages.
+        --flow-resume-count=N Sets the queue's flow resume threshold to N total messages.
+

+ Flow thresholds may also be specified in the + queue.declare method, via the + arguments parameter map. The following keys can be + provided in the arguments map for setting flow thresholds: +

Table 1.20. Queue Declare Method Flow Control Arguments

Key	Value
qpid.flow_stop_size	integer - queue's flow stop threshold value in bytes
qpid.flow_resume_size	integer - queue's flow resume threshold value in bytes
qpid.flow_stop_count	integer - queue's flow stop threshold value as a message count
qpid.flow_resume_count	integer - queue's flow resume threshold value as a message count

+ The user may disable flow control on a per queue basis by setting + the flow-stop-size and flow-stop-count to zero for the queue. +

+ The current state of flow control for a given queue can be + determined by the "flowStopped" statistic. This statistic is + available in the queue's QMF management object. The value of + flowStopped is True when the queue's capacity has exceeded the + flow stop threshold. The value of flowStopped is False when the + queue is no longer blocking due to flow control. +

+ A queue will also track the number of times flow control has been + activated. The "flowStoppedCount" statistic is incremented each time + the queue's capacity exceeds a flow stop threshold. This statistic can + be used to monitor the activity of flow control for any given queue + over time. +

Table 1.21. Flow Control Statistics available in Queue's QMF Class

Statistic Name	Type	Description
flowStopped	Boolean	If true, producers are blocked by flow control.
flowStoppedCount	count32	Number of times flow control was activated for this queue

Prev	Up	Next
1.7. + Queue State Replication +	Home	1.9. + AMQP compatibility +

+ +

+ + + +

+ + http://git-wip-us.apache.org/repos/asf/qpid-site/blob/eff0fe55/content/releases/qpid-cpp-1.35.0/cpp-broker/book/queue-state-replication.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-cpp-1.35.0/cpp-broker/book/queue-state-replication.html b/content/releases/qpid-cpp-1.35.0/cpp-broker/book/queue-state-replication.html new file mode 100644 index 0000000..9a87e51 --- /dev/null +++ b/content/releases/qpid-cpp-1.35.0/cpp-broker/book/queue-state-replication.html @@ -0,0 +1,372 @@ + + + + + queue-state-replication.html - Apache Qpid™ + + + + + + + + + + + + + +

+ + +

+ + + + + +

+ + +

1.7. + Queue State Replication +
Prev	Chapter 1. + Running the AMQP Messaging Broker +	Next

1.7. + Queue State Replication +

1.7.1. + Asynchronous + Replication of Queue State +

1.7.1.1. + Overview +

+ There is support in qpidd for selective asynchronous replication + of queue state. This is achieved by: +

+ (a) enabling event generation for the queues in question +

+ (b) loading a plugin on the 'source' broker to encode those + events as messages on a replication queue (this plugin is + called + replicating_listener.so) +

+ (c) loading a custom exchange plugin on the 'backup' broker (this + plugin is called replication_exchange.so) +

+ (d) creating an instance of the replication exchange type on the + backup broker +

+ (e) establishing a federation bridge between the replication + queue on the source broker and the replication exchange on the + backup broker +

+ The bridge established between the source and backup brokers for + replication (step (e) above) should have acknowledgements turned + on (this may be done through the --ack N option to qpid-route). + This ensures that replication events are not lost if the bridge + fails. +

+ The replication protocol will also eliminate duplicates to ensure + reliably replicated state. Note though that only one bridge per + replication exchange is supported. If clients try to publish to + the replication exchange or if more than a the single required + bridge from the replication queue on the source broker is + created, replication will be corrupted. (Access control may be + used to restrict access and help prevent this). +

+ The replicating event listener plugin (step (b) above) has the + following options: +

+Queue Replication Options:
+  --replication-queue QUEUE                      Queue on which events for
+                                                 other queues are recorded
+  --replication-listener-name NAME (replicator)  name by which to register the
+                                                 replicating event listener
+  --create-replication-queue                     if set, the replication will
+                                                 be created if it does not
+                                                 exist
+

+ The name of the queue is required. It can either point to a + durable queue whose definition has been previously recorded, or + the --create-replication-queue option can be specified in which + case the queue will be created a simple non-durable queue if it + does not already exist. +

1.7.1.2. + Use with + Clustering +

+ The source and/or backup brokers may also be clustered brokers. + In this case the federated bridge will be re-established between + replicas should either of the originally connected nodes fail. + There are however the following limitations at present: +

The backup site does not process membership updates after it + establishes the first connection. In order for newly added + members on a source cluster to be eligible as failover targets, + the bridge must be recreated after those members have been added + to the source cluster. +

New members added to a backup cluster will not receive + information about currently established bridges. Therefore in + order to allow the bridge to be re-established from these members + in the event of failure of older nodes, the bridge must be + recreated after the new members have joined. +

Only a single URL can be passed to create the initial link + from backup site to the primary site. this means that at the time + of creating the initial connection the initial node in the + primary site to which the connection is made needs to be running. + Once connected the backup site will receive a membership update + of all the nodes in the primary site, and if the initial + connection node in the primary fails, the link will be + re-established on the next node that was started (time) on the + primary site. +

+ Due to the acknowledged transfer of events over the bridge (see + note above) manual recreation of the bridge and automatic + re-establishment of te bridge after connection failure (including + failover where either or both ends are clustered brokers) will + not result in event loss. +

1.7.1.3. + Operations + on Backup Queues +

+ When replicating the state of a queue to a backup broker it is + important to recognise that any other operations performed + directly on the backup queue may break the replication. +

+ If the backup queue is to be an active (i.e. accessed by clients + while replication is on) only enqueues should be selected + for + replication. In this mode, any message enqueued on the source + brokers copy of the queue will also be enqueued on the backup + brokers copy. However not attempt will be made to remove messages + from the backup queue in response to removal of messages from the + source queue. +

1.7.1.4. + Selecting + Queues for Replication +

+ Queues are selected for replication by specifying the types of + events they should generate (it is from these events that the + replicating plugin constructs messages which are then pulled and + processed by the backup site). This is done through options + passed to the initial queue-declare command that creates the + queue and may be done either through qpid-config or similar + tools, or by the application. +

+ With qpid-config, the --generate-queue-events options is used: +

+    --generate-queue-events N
+                         If set to 1, every enqueue will generate an event that can be processed by
+                         registered listeners (e.g. for replication). If set to 2, events will be
+                         generated for enqueues and dequeues
+

+ From an application, the arguments field of the queue-declare + AMQP command is used to convey this information. An entry should + be added to the map with key 'qpid.queue_event_generation' and an + integer value of 1 (to replicate only enqueue events) or 2 (to + replicate both enqueue and dequeue events). +

+ Applications written using the c++ client API may fine the + qpid::client::QueueOptions class convenient. This has a + enableQueueEvents() method on it that can be used to set the + option (the instance of QueueOptions is then passed as the value + of the arguments field in the queue-declare command. The boolean + option to that method should be set to true if only enequeue + events should be replicated; by default it is false meaning that + both enqueues and dequeues will be replicated. E.g. +

+    QueueOptions options;
+    options.enableQueueEvents(false);
+    session.queueDeclare(arg::queue="my-queue", arg::arguments=options);
+

1.7.1.5. + Example +

+ Lets assume we will run the primary broker on host1 and the + backup on host2, have installed qpidd on both and have the + replicating_listener and replication_exchange plugins in qpidd's + module directory(*1). +

+ On host1 we start the source broker and specifcy that a queue + called 'replication' should be used for storing the events until + consumed by the backup. We also request that this queue be + created (as transient) if not already specified: +

+    qpidd --replication-queue replication-queue --create-replication-queue true --log-enable info+
+

+ On host2 we start up the backup broker ensuring that the + replication exchange module is loaded: +

+    qpidd
+

+ We can then create the instance of that replication exchange that + we will use to process the events: +

+    qpid-config -a host2 add exchange replication replication-exchange
+

+ If this fails with the message "Exchange type not implemented: + replication", it means the replication exchange module was + not + loaded. Check that the module is installed on your system and if + necessary provide the full path to the library. +

+ We then connect the replication queue on the source broker with + the replication exchange on the backup broker using the + qpid-route command: +

+    qpid-route --ack 50 queue add host2 host1 replication-exchange replication-queue
+

+ The example above configures the bridge to acknowledge messages + in batches of 50. +

+ Now create two queues (on both source and backup brokers), one + replicating both enqueues and dequeues (queue-a) and the + other + replicating only dequeues (queue-b): +

+    qpid-config -a host1 add queue queue-a --generate-queue-events 2
+    qpid-config -a host1 add queue queue-b --generate-queue-events 1
+
+    qpid-config -a host2 add queue queue-a
+    qpid-config -a host2 add queue queue-b
+

+ We are now ready to use the queues and see the replication. +

+ Any message enqueued on queue-a will be replicated to the backup + broker. When the message is acknowledged by a client connected to + host1 (and thus dequeued), that message will be removed from the + copy of the queue on host2. The state of queue-a on host2 will + thus mirror that of the equivalent queue on host1, albeit with a + small lag. (Note + however that we must not have clients connected to host2 publish + to-or consume from- queue-a or the state will fail to replicate + correctly due to conflicts). +

+ Any message enqueued on queue-b on host1 will also be enqueued on + the equivalent queue on host2. However the acknowledgement and + consequent dequeuing of messages from queue-b on host1 will have + no effect on the state of queue-b on host2. +

+ (*1) If not the paths in the above may need to be modified. E.g. + if using modules built from a qpid svn checkout, the following + would be added to the command line used to start qpidd on host1: +

+    --load-module <path-to-qpid-dir>/src/.libs/replicating_listener.so
+

+ and the following for the equivalent command line on host2: +

+    --load-module <path-to-qpid-dir>/src/.libs/replication_exchange.so
+

Prev	Up	Next
1.6. LVQ - Last Value Queue	Home	1.8. + Producer Flow Control +

+ +

+ + + +

+ + http://git-wip-us.apache.org/repos/asf/qpid-site/blob/eff0fe55/content/releases/qpid-cpp-1.35.0/cpp-broker/cpp-broker-book.pdf ---------------------------------------------------------------------- diff --git a/content/releases/qpid-cpp-1.35.0/cpp-broker/cpp-broker-book.pdf b/content/releases/qpid-cpp-1.35.0/cpp-broker/cpp-broker-book.pdf new file mode 100755 index 0000000..50f781b Binary files /dev/null and b/content/releases/qpid-cpp-1.35.0/cpp-broker/cpp-broker-book.pdf differ http://git-wip-us.apache.org/repos/asf/qpid-site/blob/eff0fe55/content/releases/qpid-cpp-1.35.0/index.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-cpp-1.35.0/index.html b/content/releases/qpid-cpp-1.35.0/index.html new file mode 100644 index 0000000..09286d4 --- /dev/null +++ b/content/releases/qpid-cpp-1.35.0/index.html @@ -0,0 +1,230 @@ + + + + + Qpid C++ 1.35.0 - Apache Qpid™ + + + + + + + + + + + + + +

+ + +

+ + + + + +

+ + +

Qpid C++ 1.35.0

+ +

Qpid C++ offers a connection-oriented messaging API and a message +broker written in C++ that stores, routes, and forwards messages using +AMQP. More about Qpid.

+ +

For a detailed list of the changes in this release, see the release +notes.

+ +

It's important to verify the +integrity of the +files you download.

+ +

Source archives

+ + + + + + + + + + + + + + + + +

Content	Download	Verify
C++ broker, Qpid Messaging API (C++)	qpid-cpp-1.35.0.tar.gz	ASC, MD5, SHA1

+ +

Components

+ + + + + + + + + + + + + + + + + + + + + + + + +

Component	Languages	Platforms	AMQP versions
C++ broker	C++	Linux, Windows	1.0, 0-10
Qpid Messaging API	C++	Linux, Windows	1.0, 0-10

+ +

Documentation

+ +

More information

+ +

+ + + + +

+ + + +

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

Project

Messaging APIs

Servers and tools

Resources

AMQP Messaging Broker (Implemented in C++)

Project

Messaging APIs

Servers and tools

Resources

Introduction

Project

Messaging APIs

Servers and tools

Resources

1.8. + Producer Flow Control +

1.8.1. + Overview +

1.8.1.1. + Example +

1.8.1.2. + Example +

1.8.2. + User Interface +

Project

Messaging APIs

Servers and tools

Resources

1.7. + Queue State Replication +

1.7.1. + Asynchronous + Replication of Queue State +

1.7.1.1. + Overview +

1.7.1.2. + Use with + Clustering +

1.7.1.3. + Operations + on Backup Queues +

1.7.1.4. + Selecting + Queues for Replication +

1.7.1.5. + Example +

Project

Messaging APIs

Servers and tools

Resources

Qpid C++ 1.35.0

Source archives

Components

Documentation

More information