Skip to content

Widhian Bramantya

coding is an art form

Menu
  • About Me
Menu
rabbitmq

Dead Letter Queues in RabbitMQ: How to Handle Failed Messages

Posted on September 8, 2025September 8, 2025 by admin

In messaging systems, not every message can be processed successfully. Some messages may be invalid, expired, or cause errors in consumers.

Instead of losing these messages, RabbitMQ provides a feature called the Dead Letter Queue (DLQ). DLQs allow you to capture, inspect, and handle failed messages safely.

By default, any message that is rejected with requeue=false or expired will go straight to the DLQ. But in real-world systems, we don’t want a message to be sent to DLQ on the first failure. Instead, we usually give the message a few retry attempts (e.g., 3 times) before moving it permanently to the DLQ.

How to Implement “Retry 3 Times Before DLQ”

There are several approaches. The simplest way:

  1. Add a retry counter to the message (via headers).
  2. If processing fails:
    • Increase the counter.
    • If counter < 3 → requeue the message (or publish back to main queue).
    • If counter ≥ 3 → reject with requeue=false, so RabbitMQ sends it to the DLQ.

System Illustration

flowchart TD
  P[Producer] --> MQ[Main Queue]
  MQ --> C[Consumer]

  C -- success --> Done[Processed OK]
  C -- fail < 3 --> Requeue[Retry again in Main Queue]
  C -- fail >= 3 --> DLX((Dead Letter Exchange)) --> DLQ[Dead Letter Queue]

Go Implementation

We’ll use the official Go client:

go get github.com/rabbitmq/amqp091-go

Step 1: Setup DLQ and Main Queue

// declare DLX and DLQ
ch.ExchangeDeclare("dlx", "direct", true, false, false, false, nil)
qDLQ, _ := ch.QueueDeclare("dead_letters", true, false, false, false, nil)
ch.QueueBind(qDLQ.Name, "failed", "dlx", false, nil)

// main queue with DLX config
args := amqp.Table{
    "x-dead-letter-exchange":    "dlx",
    "x-dead-letter-routing-key": "failed",
}
qMain, _ := ch.QueueDeclare("main_queue", true, false, false, false, args)

Step 2: Publisher – send initial messages

body := "Task X"
ch.Publish("", qMain.Name, false, false, amqp.Publishing{
    ContentType: "text/plain",
    Body:        []byte(body),
    Headers:     amqp.Table{"x-retry": int32(0)}, // start retry count
})
See also  RabbitMQ vs Kafka: Choosing the Right Messaging System for Your Project
Pages: 1 2
Category: RabbitMQ

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Linkedin

Widhian Bramantya

Recent Posts

  • Log Management at Scale: Integrating Elasticsearch with Beats, Logstash, and Kibana
  • Index Lifecycle Management (ILM) in Elasticsearch: Automatic Data Control Made Simple
  • Blue-Green Deployment in Elasticsearch: Safe Reindexing and Zero-Downtime Upgrades
  • Maintaining Super Large Datasets in Elasticsearch
  • Elasticsearch Best Practices for Beginners
  • Implementing the Outbox Pattern with Debezium
  • Production-Grade Debezium Connector with Kafka (Postgres Outbox Example – E-Commerce Orders)
  • Connecting Debezium with Kafka for Real-Time Streaming
  • Debezium Architecture – How It Works and Core Components
  • What is Debezium? – An Introduction to Change Data Capture
  • Offset Management and Consumer Groups in Kafka
  • Partitions, Replication, and Fault Tolerance in Kafka
  • Delivery Semantics in Kafka: At Most Once, At Least Once, Exactly Once
  • Producers and Consumers: How Data Flows in Kafka
  • Kafka Architecture Explained: Brokers, Topics, Partitions, and Offsets
  • Getting Started with Apache Kafka: Core Concepts and Use Cases
  • Security Best Practices for RabbitMQ in Production
  • Understanding RabbitMQ Virtual Hosts (vhosts) and Their Uses
  • RabbitMQ Performance Tuning: Optimizing Throughput and Latency
  • High Availability in RabbitMQ: Clustering and Mirrored Queues Explained

Recent Comments

  1. Playing with VPC AWS (Part 2) – Widhian's Blog on Playing with VPC AWS (Part 1): VPC, Subnet, Internet Gateway, Route Table, NAT, and Security Group
  2. Basic Concept of ElasticSearch (Part 3): Translog, Flush, and Refresh – Widhian's Blog on Basic Concept of ElasticSearch (Part 1): Introduction
  3. Basic Concept of ElasticSearch (Part 2): Architectural Perspective – Widhian's Blog on Basic Concept of ElasticSearch (Part 3): Translog, Flush, and Refresh
  4. Basic Concept of ElasticSearch (Part 3): Translog, Flush, and Refresh – Widhian's Blog on Basic Concept of ElasticSearch (Part 2): Architectural Perspective
  5. Basic Concept of ElasticSearch (Part 1): Introduction – Widhian's Blog on Basic Concept of ElasticSearch (Part 2): Architectural Perspective

Archives

  • October 2025
  • September 2025
  • August 2025
  • November 2021
  • October 2021
  • August 2021
  • July 2021
  • June 2021
  • March 2021
  • January 2021

Categories

  • Debezium
  • Devops
  • ElasticSearch
  • Golang
  • Kafka
  • Lua
  • NATS
  • Programming
  • RabbitMQ
  • Redis
  • VPC
© 2025 Widhian Bramantya | Powered by Minimalist Blog WordPress Theme