Skip to content

when a deadletterhandler panics grabbit fails to reject the message #135

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
rhinof opened this issue Aug 21, 2019 · 0 comments
Closed

when a deadletterhandler panics grabbit fails to reject the message #135

rhinof opened this issue Aug 21, 2019 · 0 comments
Labels
bug Something isn't working

Comments

@rhinof
Copy link
Contributor

rhinof commented Aug 21, 2019

In case the deadletter handler panics grabbit fails to reject the message leaving it permanently in "delivered" state and effectively stops the service

To Reproduce

  1. create a bus instance listening to the dlq
  2. register a deadletter handler on a dlq bound to a dlx
  3. reject a message to the dlx from another service
  4. when the deadletter handler is called panic

Expected behavior
The message gets queued back and the handler reprocesses it

Actual behavior
The message remains in the delivered state and the service stops consuming messages from the dlq

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant