Configure RabbitMQ quorum queue delivery limit to handle poison messages

domain: rabbitmq · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Declare a quorum queue with a delivery limit argument: x-queue-type=quorum and x-delivery-limit=<n> where n is the maximum number of failed delivery attempts before the message is dead-lettered
  2. Configure a dead-letter exchange on the queue so rejected messages are routed: x-dead-letter-exchange=dlx-name and x-dead-letter-routing-key=dlq-routing-key
  3. Consume from the queue; on each redelivery the x-delivery-count header is incremented by the broker
  4. When x-delivery-count reaches the delivery limit the message is dropped or routed to the DLX depending on whether a DLX is configured
  5. Apply or change the limit via policy rather than queue arguments to allow live updates: rabbitmqctl set_policy quorum-dl '.*' '{"delivery-limit": 5}' --apply-to quorum_queues
  6. Monitor the dead-letter queue for poison message accumulation using the management UI or rabbitmqctl list_queues name messages

Known gotchas

Related routes

Configure RabbitMQ quorum queue x-delivery-limit to automatically dead-letter poison messages after N delivery attempts
rabbitmq.com · 6 steps · unrated
Choose and configure RabbitMQ quorum queues over classic queues
rabbitmq.com · 5 steps · unrated
configure message priority ordering on rabbitmq quorum queues
rabbitmq.com · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans