---
title: "Discussion on \"Dead letters in Spring Boot: why RabbitMQ messages end up in the DLQ, and how to replay them\" | Hashnode"
description: "Discussion on \"Dead letters in Spring Boot: why RabbitMQ messages end up in the DLQ, and how to replay them\". Why a failing @RabbitListener ends up in the DLQ, which Spring AMQP settings decide it, and how to put the messages back afterwards."
url: "https://hashnode.com/posts/dead-letters-in-spring-boot-why-rabbitmq-messages-end-up-in-the-dlq-and-how-to-replay-them/6acc9265d3321284aba8b838"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Dead letters in Spring Boot: why RabbitMQ messages end up in the DLQ, and how to replay them](https://warrenops.hashnode.dev/dead-letters-in-spring-boot-why-rabbitmq-messages-end-up-in-the-dlq-and-how-to-replay-them?utm_source=hashnode&utm_medium=feed)

Why a failing @RabbitListener ends up in the DLQ, which Spring AMQP settings decide it, and how to put the messages back afterwards.

Oct 12 · 7 min read · warrenops.hashnode.dev  
Read the article

-   [#rabbitmq](https://hashnode.com/tag/rabbitmq)
-   [#spring-boot](https://hashnode.com/tag/spring-boot)
-   [#java](https://hashnode.com/tag/java)
-   [#devops](https://hashnode.com/tag/devops)

## Written by

[Viktor](https://hashnode.com/@viba88)

@viba88

  
[View profile](https://hashnode.com/@viba88)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
