TIBCO Enterprise Message Service

Queuetibco-ems

JMS broker with persistent, non-persistent and reliable delivery modes.

Provider: default
Kind: Queue
Category: Messaging
Official docs: https://docs.tibco.com/pub/ems/8.6.0/doc/html/GUID-FD538023-D7B6-464B-9AAD-F3E603AC34EE.html

Properties · 5 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
deliveryMode · component property	enum	persistent \| non-persistent \| reliable-delivery	no	persistent	inherited
faultTolerance · 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	inherited
replay	boolean	—	no	false	▸ false
retentionDays	integer	—	no	—	inherited
role	enum	work \| dlq \| retry \| offline-mailbox \| frontier	no	work	inherited
routing · component property	boolean	—	no	false	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: "tibco-ems", component: "tibco-ems" }

Other Queue products · 23

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# TIBCO Enterprise Message Service: JMS broker whose delivery modes are PERSISTENT, NON_PERSISTENT and
3# the EMS extension RELIABLE_DELIVERY; only PERSISTENT messages are written to the server store
4# ("Message Delivery Modes", "How EMS Manages Persistent Messages").
5schemaVersion: "1"
6type: "component"
7id: "tibco-ems"
8kind: "queue"
9provider: "default"
10docs: "https://docs.tibco.com/pub/ems/8.6.0/doc/html/GUID-FD538023-D7B6-464B-9AAD-F3E603AC34EE.html"
11defaults:
12  delivery: "at-least-once"
13  ordering: "none"
14  deadLetterQueue: false
15  replay: false
16  managed: false
17properties:
18  deliveryMode:
19    type: "enum"
20    values: ["persistent", "non-persistent", "reliable-delivery"]
21    default: "persistent"
22  faultTolerance:
23    type: "boolean"
24    default: false
25  routing:
26    type: "boolean"
27    default: false

The same page as markdown, for an agent: /catalogue/components/tibco-ems.md