Dead Letter Queues
- Last UpdatedFeb 18, 2025
- 2 minute read
AVEVA™ Production Management uses dead letter queues to accumulate unprocessed messages for external integrations.
If AVEVA Production Management cannot successfully send a message, AVEVA Production Management sends the message to a dead letter queue that resides in the AVEVA Production Management internal messaging system. You may want to periodically examine the dead letter queues for unprocessed commands.
Queue names
|
Queue |
Name |
Reason |
|---|---|---|
|
Inbound Dead Letter Queue |
project.command_error_queue |
For unprocessed commands |
|
Outbound Dead Letter Queue |
delivery_error_queue |
For message delivery failure |
Reasons messages are sent to Dead Letter Queue
These are some of the reasons why a message might be sent to Dead Letter Queue:
-
System error - The application retries three times and then sends a message to a dead letter queue.
-
Communication issue - The application retries three times and then sends a message to a dead letter queue.
-
Message format error - The application rejects the message immediately and sends the message to a dead letter queue.
-
Business logic error - The application rejects the message immediately and sends the message to a dead letter queue.
Fixing dead letters
You can examine the contents of either Dead Letter Queue with the Rabbit MQ management console. You can attempt to fix messages and resubmit for processing. There are utilities such as the Shovel plugin that are intended for bulk moving messages back to the processing queue.
