IBM MQ
Enterprise queue-manager messaging with assured once-only delivery of persistent messages.
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| backoff | enum | none | fixed | exponential | exponential-jitter | no | — | inherited |
| clustered | boolean | — | no | false | inherited |
| deadLetterQueue | boolean | — | no | false | ▸ false |
| delivery | enum | at-most-once | at-least-once | exactly-once | yes | — | ▸ at-least-once |
| highAvailability | enum | none | multi-instance | native-ha | rdqm | no | none | 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 |
| replay | boolean | — | no | false | ▸ false |
| retentionDays | integer | — | no | — | inherited |
| role | enum | work | dlq | retry | offline-mailbox | frontier | no | work | inherited |
| transactional | boolean | — | no | true | inherited |
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.
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
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
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"
nodes:
- { id: "mq", component: "ibm-mq" }# yaml-language-server: $schema=../../schema/component.schema.json # IBM MQ: queue-manager based messaging with assured once-only delivery for persistent messages sent # under transactions; persistent messages are logged to disk ("IBM MQ Technical overview"). schemaVersion: "1" type: "component" id: "ibm-mq" kind: "queue" provider: "default" docs: "https://www.ibm.com/docs/en/ibm-mq/9.4.0?topic=ibm-mq-technical-overview" aliases: ["WebSphere MQ"] defaults: delivery: "at-least-once" ordering: "none" persistence: true deadLetterQueue: false replay: false managed: false properties: transactional: type: "boolean" default: true highAvailability: type: "enum" values: ["none", "multi-instance", "native-ha", "rdqm"] default: "none" clustered: type: "boolean" default: false