Skip to content

Topology it expects

For the reasons behind it, see Why it verifies and never creates. To build it, see Prepare the exchange and queues.

What the operator creates

Object Required by Condition
The exchange, Settings.Exchange every Open Exists. The adapter declares it passively as a topic exchange and checks nothing beyond the broker's answer. Publishes and bindings assume a topic exchange.
The management API every Open Answers GET /api/overview with a body that parses as JSON and a status below 300.
A queue per AtLeastOnce subscription, named by Topology.Queue Subscribe The rows below.

For an AtLeastOnce queue, in the order they are checked:

# Check Passes when
1 Exists a passive declare succeeds, and the management API has the queue. Otherwise ErrNoQueue.
2 Type the management API's type is quorum.
3 Delivery limit delivery_limit is present and either negative, or at least MaxDeliver - 1.
4 Dead-lettering x-dead-letter-exchange is set; x-dead-letter-strategy is at-least-once; x-overflow is reject-publish.
5 Consumer timeout MaxProcessingTime is zero, or no timeout is reported, or MaxProcessingTime plus one minute is at most the queue's timeout.
6 Binding a binding from Settings.Exchange with the routing key the subscription's Pattern translates to.

The first failing check is the one reported.

  • Settings 4 and 5 are read from the queue's argument (x-dead-letter-exchange, x-dead-letter-strategy, x-overflow, x-consumer-timeout) first, and from its effective policy (the same names without x-) second.
  • The delivery limit is the management API's delivery_limit, which includes the broker's default and a policy. It appears only after the API's statistics interval, so check 3 polls every 500 ms for up to 15 seconds and then refuses with "the management API reported no delivery limit".
  • The consumer timeout is compared only when the API reports one for the queue and the value is a number of milliseconds. A node-wide setting does not appear in the queue document, so a queue governed by one passes.
  • The dead-letter exchange is checked for being set, not for existing or having a bound queue.

Pattern translation

Subscription pattern Routing key
ends in .> the same with > replaced by #: orders.> is orders.#
> alone #
anything else unchanged, so * stays * and a literal subject is itself

What it declares

AtMostOnce has no identity to keep. Subscribe declares a transient queue and binds it to Settings.Exchange with the translated pattern:

Shape Name Durable Auto-delete Exclusive
Fanout server-named no yes yes
Competing the subscription's Group yes yes no

A competing queue is durable because RabbitMQ 4.3 refuses a transient queue that is not exclusive; the code records this as a finding of 2026-09-05. Auto-delete means the broker removes it when the last consumer cancels, so durability promises nothing. Consumers on both use automatic acknowledgement. It declares no arguments, so the queue is of the virtual host's default type.

Nothing else is declared. The publish channel, the probe channels and the consumer channels only declare passively.

Refusals

Raised by Condition Error
Open management unreachable, a status of 300 or more other than 404, or a body that is not JSON ErrManagement
Open cannot dial messaging-rabbitmq: dialling wrapping the cause
Open exchange absent ErrNoExchange
Subscribe Mode not AtMostOnce or AtLeastOnce messaging.ErrNotSupported
Subscribe queue absent ErrNoQueue
Subscribe any check above an error naming the queue and what was found
Publish no queue bound for the subject ErrUnroutable
Publish properties larger than the frame size an error giving both sizes