THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
For a detailed discussion, see the following resources:
The AMQP Distributed Transaction Classes (Java)
| Anchor | ||||
|---|---|---|---|---|
|
2.5. SSL
SSL allows IP communications between the broker(s) and client(s) to be encrypted.
...
For a detailed discussion, see the following resources:
Qpid Management Framework QMF
Qpid Management Features
| Anchor | ||||
|---|---|---|---|---|
|
...
For a detailed discussion, see the following resource:
Qpid Management Framework QMF
| Anchor | ||||
|---|---|---|---|---|
|
3.6. JMX Management Console
...
For a detailed discussion, see the following resource:
QMan - Qpid Management bridge
| Anchor | ||||
|---|---|---|---|---|
|
3.8. Selectors
The ability to filter the messages browsed or consumed from a queue. The filter is limited to message header properties.
| Anchor | ||||
|---|---|---|---|---|
|
3.
...
9. Replication
Asynchronous replication of queue state through the use of events on a secondary broker.
For a detailed discussion, see the following resource:
queue state replication
| Anchor | ||||
|---|---|---|---|---|
|
3.
...
10. Watchdog
The watchdog plug-in will kill the qpidd broker process if it becomes stuck for longer than a configured interval.
| Anchor | ||||
|---|---|---|---|---|
|
3.
...
11. XML Exchange
A plug-in exchange which can open messages and run xquery against it's XML content in order to determine routing to the appropriate queue.
| Anchor | ||||
|---|---|---|---|---|
|
3.
...
12. Last Value Queue (LVQ)
A queue in which the content is maintained as key-value pairs. Publishing to a LVQ updates the value against its key; consuming a message for a particular key allows the last value to be read. The key/value pair may or may not be consumed, depending on options.
For a detailed discussion, see the following resources:
LVQ
LVQ Example
| Anchor | ||||
|---|---|---|---|---|
|
3.
...
13. Priority Queue
Queues in which the delivery order is determined primarily by the priority of the message, and secondarily by the order of arrival.
For a detailed discussion, see the following resources:
Use Priority Queues
Qpid Design - Queue Implementation - see section on Priority Queues
| Anchor | ||||
|---|---|---|---|---|
|
3.
...
14. SASL Security
Simple Authentication and Security Layer - an industry standard framework for authentication, and implemented in Qpid.
For a detailed discussion, see the following resources:
Qpid Design - Authentication
Qpid Interoperability Documentation - Authentication mechanism interoperability
| Anchor | ||||
|---|---|---|---|---|
|
3.
...
15. BDB Store Module
An implementation of a persistence store using Oracle Berkeley Database (BDB) which provides persistence to exchanges and queues and their configurations, and to the messages on these queues. Exchanges, queues and messages must be set to be persistent before they will be persisted. In addition, only persistent queues may store persistent messages.
For a detailed discussion, see the following resource:
MessageStore Tool
| Anchor | ||||
|---|---|---|---|---|
|
3.
...
16. SQL Database Store Module
An implementation of a persistence store using a QSL database which provides persistence to exchanges and queues and their configurations, and to the messages on these queues. Exchanges, queues and messages must be set to be persistent before they will be persisted. In addition, only persistent queues may store persistent messages.
| Anchor | ||||
|---|---|---|---|---|
|
3.
...
17. Async Store Module
A Linux-only implementation of a persistence store using a combination of BDB (for exchange and queue configuration) and a custom-written asynchronous store (for message content and transactions). This store is capable of writing messages to disk at high rates through the use of DMA. Exchanges, queues and messages must be set to be persistent before they will be persisted. In addition, only persistent queues may store persistent messages.
| Anchor | ||||
|---|---|---|---|---|
|
3.
...
18. Durable Exchanges
Exchanges and their configuration are persisted so that they do not need to be recreated on recovery or on startup of a previously running broker where they were present. The exchange must be set to be persistent and there must be a store module loaded for this persistence to be active.
| Anchor | ||||
|---|---|---|---|---|
|
3.
...
19. Durable Queues
Queues and their configuration are persisted so that they do not need to be recreated on recovery or on startup of a previously running broker where they were present. The queue must be set to be persistent and there must be a store module loaded for this persistence to be active. Note also that only persistent queues can store persistent messages and recover them at recovery/startup.
| Anchor | ||||
|---|---|---|---|---|
|
3.
...
20. Durable Bindings
Bindings and their configuration are persisted so that they do not need to be recreated on recovery or on startup of a previously running broker where they were present. The exchange and the queue being bound must be set to be persistent and there must be a store module loaded for this persistence to be active.
| Anchor | ||||
|---|---|---|---|---|
|
3.
...
21. Queue Sizing Policies
The content of queues may be limited by number and/or cumulative message size. When these limits are exceeded, the queue may manage the situation by (among others) refusing to accept new messages, throttling message production, or flowing the messages to disk (see Flow-to-disk below).
| Anchor | ||||
|---|---|---|---|---|
|
3.
...
22. Flow-to-disk
Flow-to-disk is one of the mechanisms for handling queue size policy violations. This mechanism allows all messages which exceed a queue size policy to be written to disk (whether persistent or not), and the message content is released from memory. To consume the message, however, the message must first be read from the store to restore its content to the queue.
...