7.8. Queues

Reply-To: dev@qpid.apache.org Delivered-To: mailing list commits@qpid.apache.org Received: (qmail 73458 invoked by uid 99); 28 Dec 2016 10:37:22 -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; Wed, 28 Dec 2016 10:37:22 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 1CED4DFD86; Wed, 28 Dec 2016 10:37:22 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: orudyy@apache.org To: commits@qpid.apache.org Date: Wed, 28 Dec 2016 10:37:59 -0000 Message-Id: <2197f973259140b1af5db59031d4192f@git.apache.org> In-Reply-To: <9a668f1bb56f4133b558ca5211b30157@git.apache.org> References: <9a668f1bb56f4133b558ca5211b30157@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: [39/51] [partial] qpid-site git commit: Update site for 6.1.1 release of Qpid Java archived-at: Wed, 28 Dec 2016 10:37:29 -0000 http://git-wip-us.apache.org/repos/asf/qpid-site/blob/6e5b75e1/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Queues.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Queues.html b/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Queues.html new file mode 100644 index 0000000..f60c7c3 --- /dev/null +++ b/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Queues.html @@ -0,0 +1,162 @@ + + + + + 7.8. Queues - Apache Qpid™ + + + + + + + + + + + + + +

+ + +

+ + + + + +

+ + +

7.8. Queues
Prev	Chapter 7. Managing Entities	Next

Queues are named entities that + hold/buffer messages for later delivery to consumer applications.

Queues can be managed using the HTTP or AMQP channels.

7.8.1. Types

The Broker supports four different queue types, each with different delivery semantics.

Standard - a simple First-In-First-Out (FIFO) queue
Priority - delivery order depends on the priority of each message
Sorted - + delivery order depends on the value of the sorting key property in each message
Last Value + Queue - also known as an LVQ, retains only the last (newest) message received + with a given LVQ key value

7.8.2. Attributes

Name of the queue. Message consumers and browsers refer to this + name when they wish to subscribe to queue to receive messages from it.
Type of the queue. Can be either standard, priority, sorted, or lvq.
Durable. Whether the queue survives a restart. Messages on a + non durable queue do not survive a restart even if they are marked persistent.
Maximum/Minimum TTL. Defines a maximum and minimum + time-to-live. Messages arriving with ttl larger than the maximum will be overridden by + the maximum. Similarly, messages arriving with tll less than the minimum (or no ttl at + all), will be overridden by the minimum.
Changing these values affects only new arrivals, existing messages already on the + queue are not affected.
Message persistent override. Allow message persistent settings + of incoming messages to be overridden. Changing this value affects only new arrivals, + existing messages on the queue are not affected.
Queue capacity. Queues have the ability to limit the of the + cumulative size of all the messages contained within the store. This feature is + described in detail Section 9.2, “Disk Space Management”.
Alerting Thresholds. Queues have the ability to alert on a + variety of conditions: total queue depth exceeded a number or size, message age exceeded + a threshold, message size exceeded a threshold. These thresholds are soft. See Appendix D, Queue Alerts
Maximum Delivery Count/Alternate Exchange. See Section 9.4, “Handing Undeliverable Messages”
Message Groups. See Section 4.7.3, “Messaging Grouping”

7.8.3. Children

Binding

7.8.4. Lifecycle

Not supported

Prev	Up	Next
7.7. Exchanges	Home	7.9. Consumers

+ +

+ + + +

+ 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/6e5b75e1/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-RemoteReplicationNodes.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-RemoteReplicationNodes.html b/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-RemoteReplicationNodes.html new file mode 100644 index 0000000..2a56abd --- /dev/null +++ b/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-RemoteReplicationNodes.html @@ -0,0 +1,167 @@ + + + + + 7.6. Remote Replication Nodes - Apache Qpid™ + + + + + + + + + + + + + +

+ + +

+ + + + + +

+ + +

7.6. Remote Replication Nodes
Prev	Chapter 7. Managing Entities	Next

7.6. Remote Replication Nodes

Used for HA only. A remote replication node is a representation of another virtualhost node + in the group. Remote replication nodes are not created directly. Instead the system + automatically creates a remote replication node for every node in the group. It serves to + provide a view of the whole group from every node in the system.

7.6.1. Attributes

Name the remote replication node. This is the name of the + remote virtualhost node
Role. Indicates the role that the remote node is playing in the + group at this moment.
- MASTER - Remote node is a master.
- REPLICA - Remote node is a replica.
- UNREACHABLE - Remote node unreachable from this node. + This remote note may be down, or an network problem may prevent it from being + contacted.
+
Join time. Time when first contact was established with this + node.
Last known transaction id. Last transaction id reported + processed by node. This is an internal transaction counter and does not relate to any + value available to the messaging clients. This value can only be used to determine the + node is up to date relative to others in the group.

7.6.2. Children

None

7.6.3. Lifecycle

Delete. Causes the remote node to be permanently removed from + the group. This operation should be used when the virtualhost node cannot be deleted + from its own Broker, for instance, if a Broker has been destroyed by machine + failure.

7.6.4. Operations

Transfer Master. Initiates a process where a master is moved to + anther node in the group. The transfer sequence is as follows.
1. Group waits until the proposed master is reasonable up to date.
2. Any in-flight transactions on the current master are blocked.
3. The current master awaits the proposed master to become up to date.
4. The mastership is transferred. This will automatically disconnect messaging + clients from the old master, and in-flight transactions are rolled back. Messaging + clients reconnect to the new master.
5. The old master will rejoin as a replica.
+

Prev	Up	Next
7.5. VirtualHosts	Home	7.7. Exchanges

+ +

+ + + +

+ + http://git-wip-us.apache.org/repos/asf/qpid-site/blob/6e5b75e1/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Truststores.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Truststores.html b/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Truststores.html new file mode 100644 index 0000000..23acb32 --- /dev/null +++ b/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Truststores.html @@ -0,0 +1,180 @@ + + + + + 7.13. Truststores - Apache Qpid™ + + + + + + + + + + + + + +

+ + +

+ + + + + +

+ + +

7.13. Truststores
Prev	Chapter 7. Managing Entities	Next

7.13. Truststores

+ Truststores + have a number of roles within + the Broker. +

A truststore is required by a Port in order to support SSL client authentication.
Truststores have a optional role in end to end message encryption. The Broker acts as a + + Key Server + + so that publishing applications have convenient access to recipient's public keys. +
Some authentication providers also use a truststore when connecting to authentication systems that + are protected by a private issuer + SSL certificate. +

7.13.1. Types

The following truststore types are supported.

File Trust Store. This type accepts the standard JKS + truststore format understood by Java and Java tools such as keytool.
Non Java Trust Store. A non java trust store accepts key + material in PEM and DER file formats. Either a path to the certificate on the server can be specified using the file:// protocol or the certificate can be uploaded with the data:// protocol
Managed Certificate Store. This type accepts key + material in PEM and DER file formats. Contrary to the Non Java Trust Store this store allows the user to add multiple certificates and stores them in the broker configuration.
Site Specific Trust Store. This type will download a certificate from the provided SSL/TLS enabled URL. Note that you must specify both the protocol and the port. Example: https://example.com:443

7.13.2. Attributes

Name the truststore. Used to identify the + truststore.
Exposed as Message Source. If enabled, the Broker + will distribute certificates contained within the trustore to clients. + Used by the end to end message encryption feature.

The following attributes apply to File Trust Stores only.

Path. Path to truststore file
Truststore password. Password used to secure the truststore
Important
The password of the certificate used by the Broker must match the password of the keystore + itself.
Certificate Alias. An optional way of specifying + which certificate the broker should use if the keystore contains multiple + entries.
Manager Factory Algorithm. In keystores the have more + than one certificate, the alias identifies the certificate to be + used.
Key Store Type. Type of Keystore.
Peers only. When "Peers Only" option is selected for + the Truststore it will allow authenticate only those clients that present a + certificate exactly matching a certificate contained within the Truststore + database.

The following attributes apply to Non Java Trust Stores + only.

Certificates. The cerificate(s) in DER or PEM + format.

7.13.3. Children

None

7.13.4. Lifecycle

Not supported

Prev	Up	Next
7.12. Keystores	Home	7.14. Group Providers

+ +

+ + + +

+ + http://git-wip-us.apache.org/repos/asf/qpid-site/blob/6e5b75e1/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Virtualhost-Nodes.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Virtualhost-Nodes.html b/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Virtualhost-Nodes.html new file mode 100644 index 0000000..6c9a758 --- /dev/null +++ b/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Virtualhost-Nodes.html @@ -0,0 +1,177 @@ + + + + + 7.4. Virtualhost Nodes - Apache Qpid™ + + + + + + + + + + + + + +

+ + +

+ + + + + +

+ + +

7.4. Virtualhost Nodes
Prev	Chapter 7. Managing Entities	Next

7.4. Virtualhost Nodes

Virtualhost nodes can only be managed by the HTTP management channel.

7.4.1. Types

The following vir tualhost nodes types are supported.

BDB - Node backed with Oracle BDB ^[6]
BDB HA - Node backed with Oracle BDB utilising High + Availability
DERBY - Node backed with Apache Derby
JDBC - Node backed with an external database ^[7]
JSON - Node backed with a file containing json
Memory - In-memory node (changes lost on Broker restart)

7.4.2. Attributes

Name the virtualhost node.
Default Virtual Host Node. If true, messaging clients which do + not specify a virtualhost name will be connected to the virtualhost beneath this node.
Store Path or JDBC URL. Refers the location used to store the + configuration of the virtualhost.
Role (HA only). The role that this node is currently playing in + the group.
- MASTER - Virtualhost node is a master.
- REPLICA - Virtualhost node is a replica.
- WAITING - Virtualhost node is awaiting an election result, or may be awaiting + more nodes to join in order that an election may be held.
- DETACHED - Virtualhost node is disconnected from the group.
Priority (HA only). The priority of this node when elections + occurs. The attribute can be used to make it more likely for a node to be elected than + other nodes, or disallow the node from never being elected at all. See Section 10.4.3, “Node Priority”
Minimum Number Of Nodes (HA only - groups of three or more). + Allows the number of nodes required to hold an election to be reduced in order that + service can be restore when less than quorum nodes are present. See Section 10.4.4, “Required Minimum Number Of Nodes”
Allow this node to operate solo (HA only - groups of two). Allows a single + node in a two node group to operate solo. See Section 10.4.5, “Allow to Operate Solo”

7.4.3. Children

+ Virtualhost +
+ Remote + Replication Nodes +

7.4.4. Lifecycle

Stop. Stops the virtualhost node. This closes any existing + messaging connections to the virtualhost and prevents new ones. Any inflight + transactions are rolled back. Non durable queues and exchanges are lost. Transient + messages or persistent messages on non-durable queues are lost.
When HA is in use, stopping the virtualhost node stops the virtualhost node from + participating in the group. If the node was in the master role, the remaining nodes will + try to conduct an election and elect a new master. If the node was in the replica role, + the node will cease to keep up to date with later transactions. A stopped node does not + vote in elections. Other nodes in the group will report the stopped node as + unreachable.
Start. Activates the virtualhost node.
Delete. Deletes the virtualhost node and the virtualhost + contained within it. All exchanges and queues, any the messages contained within it are + removed. In the HA case, deleting the virtualhost node causes it be removed permanently + from the group.

^[6]Oracle BDB JE is optional. See Section E.3, “Installing Oracle BDB JE”.

^[7]JDBC 4.0 compatible drivers must be available. See Section E.2, “Installing External JDBC Driver”

Prev	Up	Next
7.3. Broker	Home	7.5. VirtualHosts

+ +

+ + + +

+ + http://git-wip-us.apache.org/repos/asf/qpid-site/blob/6e5b75e1/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Virtualhosts.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Virtualhosts.html b/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Virtualhosts.html new file mode 100644 index 0000000..42e7c94 --- /dev/null +++ b/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Management-Managing-Virtualhosts.html @@ -0,0 +1,171 @@ + + + + + 7.5. VirtualHosts - Apache Qpid™ + + + + + + + + + + + + + +

+ + +

+ + + + + +

+ + +

7.5. VirtualHosts
Prev	Chapter 7. Managing Entities	Next

7.5. VirtualHosts

A virtualhost is a independent namespace in which messaging is performed. Virtualhosts are + responsible for the storage of message data.

Virtualhosts can only be managed by the HTTP management channel.

7.5.1. Types

The following virtualhost types are supported.

BDB - Virtualhost backed with Oracle BDB ^[8]
BDB HA - Virtualhost backed with Oracle BDB utilising High Availability
DERBY - Virtualhost backed with Apache Derby
JDBC - Virtualhost backed with an external database ^[9]
Memory - In-memory nod e (changes lost on Broker restart)
Provided - Virtualhost that co-locates message data within the parent virtualhost + node ^[10].

7.5.2. Context

use_async_message_store_recovery Controls the background recovery + feature.

7.5.3. Attributes

Name the virtualhost. This is the name the messaging clients + refer to when forming a connection to the Broker.
Store Path/JDBC URL. Refers the file system location or + database URL used to store the message data.
Store overflow/underflow. Some virtualhosts have the ability to + limit the of the cumulative size of all the messages contained within the store. This + feature is described in detail Section 9.2, “Disk Space Management”.
Connection thread pool size. Number of worker threads + used to perform messaging with connected clients.
Defaults to 64 or double the maximum number of available processors, whichever + is the larger.
Number of selectors. Number of worker threads + used from the thread pool to dispatch I/O activity to the worker threads.
Defaults to one eighth of the thread pool size. Minimum 1.
Store transaction timeouts. Warns of long running producer + transactions. See Section 9.3, “Producer Transaction Timeout”
Synchronization policy. HA only. See Section 10.4.2, “Synchronization Policy”

7.5.4. Children

+ Exchange +
+ Queue +

7.5.5. Lifecycle

Stop. Stops the virtualhost. This closes any existing messaging + connections to the virtualhost and prevents new ones. Any inflight transactions are + rolled back. Non durable queues and non durable exchanges are lost. Transient messages + or persistent messages on non-durable queues are lost.
Start. Activates the virtualhost.

^[8]Oracle BDB JE is optional. See Section E.3, “Installing Oracle BDB JE”.

^[9]JDBC 4.0 compatible drivers must be available. See Section E.2, “Installing External JDBC Driver”

^[10]Not available if Virtualhost Node type is JSON.

Prev	Up	Next
7.4. Virtualhost Nodes	Home	7.6. Remote Replication Nodes

+ +

+ + + +

+ + http://git-wip-us.apache.org/repos/asf/qpid-site/blob/6e5b75e1/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Miscellaneous-Installing-External-JDBC-Driver.html ---------------------------------------------------------------------- diff --git a/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Miscellaneous-Installing-External-JDBC-Driver.html b/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Miscellaneous-Installing-External-JDBC-Driver.html new file mode 100644 index 0000000..b343cb0 --- /dev/null +++ b/content/releases/qpid-java-6.1.1/java-broker/book/Java-Broker-Miscellaneous-Installing-External-JDBC-Driver.html @@ -0,0 +1,148 @@ + + + + + E.2. Installing External JDBC Driver - Apache Qpid™ + + + + + + + + + + + + + +

+ + +

+ + + + + +

+ + +

E.2. Installing External JDBC Driver
Prev	Appendix E. Miscellaneous	Next

E.2. Installing External JDBC Driver

In order to use a JDBC Virtualhost Node or a JDBC Virtualhost, you must make the + Database's JDBC 4.0 compatible drivers available on the Broker's classpath. To do this copy + the driver's JAR file into the ${QPID_HOME}/lib folder.

Unix:
+cp driver.jar qpid-broker-6.1.1/lib

Windows:
+copy driver.jar qpid-broker-6.1.1\lib

Prev	Up	Next
Appendix E. Miscellaneous	Home	E.3. Installing Oracle BDB JE

+ +

+ + + +

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

7.8. Queues

7.8.1. Types

7.8.2. Attributes

7.8.3. Children

7.8.4. Lifecycle

Project

Messaging APIs

Servers and tools

Resources

7.6. Remote Replication Nodes

7.6.1. Attributes

7.6.2. Children

7.6.3. Lifecycle

7.6.4. Operations

Project

Messaging APIs

Servers and tools

Resources

7.13. Truststores

7.13.1. Types

7.13.2. Attributes

Important

7.13.3. Children

7.13.4. Lifecycle

Project

Messaging APIs

Servers and tools

Resources

7.4. Virtualhost Nodes

7.4.1. Types

7.4.2. Attributes

7.4.3. Children

7.4.4. Lifecycle

Project

Messaging APIs

Servers and tools

Resources

7.5. VirtualHosts

7.5.1. Types

7.5.2. Context

7.5.3. Attributes

7.5.4. Children

7.5.5. Lifecycle

Project

Messaging APIs

Servers and tools

Resources

E.2. Installing External JDBC Driver