Apache Qpid Broker-J

Pure-Java AMQP message broker supporting AMQP 0-8 through 1.0.

Provider: default
Kind: Queue
Category: Messaging
Official docs: https://qpid.apache.org/releases/qpid-broker-j-9.2.1/book/Java-Broker-Concepts-Queues.html

Properties · 6 set by this component

property	type	values	required	kind default	this component
backoff	enum	none \| fixed \| exponential \| exponential-jitter	no	—	inherited
deadLetterQueue	boolean	—	no	false	▸ false
delivery	enum	at-most-once \| at-least-once \| exactly-once	yes	—	▸ at-least-once
highAvailability · component property	boolean	—	no	false	inherited
instances	integer	—	no	—	inherited
managed	boolean	—	no	false	▸ false
maxAttempts	integer	—	no	—	inherited
ordering	enum	none \| per-key \| global	no	none	▸ none
persistence	boolean	—	no	true	▸ true
protocolVersion · component property	enum	amqp-0-8 \| amqp-0-9 \| amqp-0-9-1 \| amqp-0-10 \| amqp-1-0	no	amqp-1-0	inherited
queueType · component property	enum	standard \| priority \| sorted \| lvq	no	standard	inherited
replay	boolean	—	no	false	▸ false
retentionDays	integer	—	no	—	inherited
role	enum	work \| dlq \| retry \| offline-mailbox \| frontier	no	work	inherited

Rules that apply · 3

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

Queue without dead-letter queueerror

queue-missing-dlq

A queue that receives asynchronous traffic and has no dead-letter queue either drops poison messages or retries them forever. Neither outcome leaves anything for a human to investigate.

— all of these hold:
— the node's `deadLetterQueue` is false
— the node has at least one asynchronous incoming edge

Retry queue without dead-letter queueerror

retry-queue-without-dlq

A retry queue is where poison messages end up. With no dead-letter queue they are retried forever or dropped in silence, and nobody ever looks at the failed payment.

— all of these hold:
— the node's `role` is "retry"
— the node's `deadLetterQueue` is false

Retry queue without backoffwarning

retry-without-backoff

Retrying a transient failure at full speed turns one slow dependency into a retry storm. A retry queue backs off, preferably exponentially and with jitter.

— all of these hold:
— the node's `role` is "retry"
— any of these hold:
— the node's `backoff` has no value
— the node's `backoff` is "none"

Use it in a design

nodes:
  - { id: "qpid", component: "qpid" }

Other Queue products · 23

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Apache Qpid Broker-J: pure-Java AMQP broker (0-8 through 1.0) whose standard queue is a simple FIFO
3# and whose configuration and message stores are on-disk ("Java Broker Concepts", "Queues").
4schemaVersion: "1"
5type: "component"
6id: "qpid"
7kind: "queue"
8provider: "default"
9docs: "https://qpid.apache.org/releases/qpid-broker-j-9.2.1/book/Java-Broker-Concepts-Queues.html"
10defaults:
11  delivery: "at-least-once"
12  ordering: "none"
13  deadLetterQueue: false
14  persistence: true
15  replay: false
16  managed: false
17properties:
18  queueType:
19    type: "enum"
20    values: ["standard", "priority", "sorted", "lvq"]
21    default: "standard"
22  protocolVersion:
23    type: "enum"
24    values: ["amqp-0-8", "amqp-0-9", "amqp-0-9-1", "amqp-0-10", "amqp-1-0"]
25    default: "amqp-1-0"
26  highAvailability:
27    type: "boolean"
28    default: false

The same page as markdown, for an agent: /catalogue/components/qpid.md