tencent cloud

TDMQ for RabbitMQ

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Introduction and Selection of the TDMQ Product Series
What Is TDMQ for RabbitMQ
Strengths
Use Cases
Description of Differences Between Managed Edition and Serverless Edition
Open-Source Version Support Description
Comparison with Open-Source RabbitMQ
High Availability
Use Limits
TDMQ for RabbitMQ-Related Concepts
Regions
Related Cloud Services
Billing
Billing Overview
Pricing
Billing Example
Convert to Monthly Subscription from Hourly Postpaid
Renewal
Viewing Consumption Details
Overdue Payments
Refund
Getting Started
Getting Started Guide
Step 1: Preparations
Step 2: Creating a RabbitMQ Cluster
Step 3: Configuring a Vhost
Step 4: Using the SDK to Send and Receive Messages
Step 5: Querying a Message
Step 6: Deleting Resources
User Guide
Usage Process Guide
Configuring the Account Permission
Creating a Cluster
Configuring a Vhost
Connecting to the Cluster
Managing Messages
Configure Advanced Feature
Managing the Cluster
Viewing Monitoring Data and Configuring Alarm Policy
Use Cases
Use Instructions of Use Cases
RabbitMQ Client Use Cases
RabbitMQ Message Reliability Use Cases
Usage Instructions for MQTT Protocol Supported by RabbitMQ
Migrate Cluster
Migrating RabbitMQ to Cloud
Step 1. Purchasing a TDMQ Instance
Step 2: Migrating Metadata to the Cloud
Step 3: Enabling Dual Read-Write
API Reference (Managed Edition)
API Overview
API Reference (Serverless Edition)
History
Introduction
API Category
Making API Requests
Relevant APIs for RabbitMQ Serverless PAAS Capacity
RabbitMQ Serverless Instance Management APIs
Data Types
Error Codes
SDK Documentation
SDK Overview
Spring Boot Starter Integration
Spring Cloud Stream Integration
Java SDK
Go SDK
Python SDK
PHP SDK
Security and Compliance
Permission Management
Network Security
Deletion Protection
Change Records
CloudAudit
FAQs
Service Level Agreement
Contact Us

Configuring Dead Letter Message

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2026-01-04 15:02:28
Dead letter mechanism is a message processing method provided by RabbitMQ. Messages in the queue are marked as dead letter messages in any of the following scenarios:
1. When the requeue parameter is set to false, the consumer negatively acknowledges messages using basic.reject or basic.nack.
2. The time to live (TTL) of messages in the queue exceeds the preset TTL.
3. The number of messages in the queue has reached the set capacity limit, and the Overflow Behaviour parameter is set to reject-publish-dlx.
Processing method for dead letter messages:
If a dead letter queue (dead letter exchange) is configured, messages will be automatically routed to that queue.
If no dead letter queue is configured, messages will be automatically discarded by the system.
The mechanism provides a reliable solution for processing abnormal messages, ensuring the integrity of business message flows. For more information about the dead letter mechanism, see Dead Letter Exchanges.

Operation Steps

When creating a queue, specify a dead letter exchange. For specific steps, see Creating a Queue.
Managed Edition: Configure the dead letter exchange and dead letter Routing Key in Common Parameters:
Dead letter exchange: Specify the dead letter exchange in the drop-down list.
Dead letter Routing Key: Enter a dead letter Routing Key. It must be 1 to 255 characters in length and can only contain letters, digits, hyphens (-), underscores (_), periods (.), and at signs (@).

Serverless Edition: Specify a dead letter exchange when creating a queue.




Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan