Skip to content

Are there anyway for duplicated message to be dead letter upon published? [Question] #106

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
cha45689 opened this issue Feb 5, 2024 · 2 comments
Labels
feature Feature request

Comments

@cha45689
Copy link

cha45689 commented Feb 5, 2024

I would like to ask whether it is possible that when message is publish and consider duplicated it will be route to dead letter exchange and queue?

desired behavior

  1. there is one message with x-deduplication-header : "1" already in queue
  2. I try to publish another message with x-deduplication-header : "1"
  3. the message in 2. should be route to dead-letter-exchange / queue
@noxdafox noxdafox added the feature Feature request label Nov 6, 2024
@noxdafox
Copy link
Owner

noxdafox commented Nov 6, 2024

I am unsure whether it is possible. I will have a look at RMQ source code to see if this can be easily supported.

@noxdafox
Copy link
Owner

noxdafox commented May 5, 2025

Since 0.7.0 and RMQ v4.1.0, duplicate messages will go to the configured deadletter queue.

@noxdafox noxdafox closed this as completed May 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Feature request
Projects
None yet
Development

No branches or pull requests

2 participants