Spring Boot RabbitMQ Retry mechanism acknowledge and reject
ฝัง
- เผยแพร่เมื่อ 11 ก.ย. 2024
- Enjoy! :-)
Thank you for commenting and asking questions.
Library sign up referral link:
lbry.tv/$/invi...
Get 25 % discount on your Minecraft servers at Shockbyte.com by using this referral link:
shockbyte.com/...
Checkout or buy the Introduction to Algorithms book at Amazon:
amzn.to/2RK3Lur
The code is located here:
github.com/eki...
Follow me on twitter:
/ mikemoelnielsen
Chat on Discord:
/ discord
Support me on Patreon:
/ mikemoellernielsen
As an Amazon Associate I earn from qualifying purchases.
Check out the stuff that I like (always updated):
kit.co/MikeMoe...
Thanks buddy. This was awesome.
Glad you enjoyed it. Thank you for watching. :-)
Awesome video thanks!
No problem!
@@MikesTechCorner One question though when we a retrying for a message, the thread that was responsible for message processing would be blocked and will not be able to any other tasks right?
@@rahuldeepattri9244 You can route the failed messages to a timeout queue or use the backoff plugin
@@MikesTechCorner Thanks for your response! Agreed then spring retry mechanism on timeout queue makes more sense. And the back off plugin you mentioned is a rabbit mq plugin?
Hi Mike, isn't a missing @EnableRetry the cause of the programmatic approach failure?
I would setup a special queue for retries and then a timeout to wait for a system to come up again. Maybe a delay of 15 min or so.
How did you applied retry mechanism? please tell how you implemented at end
Try to clone the project and look in the code. I have uploaded the project and added link in the description.
Hi how can I acknowledge a message on my listener and where can I see that my message is being acknowledge from. Appreciate if you could help me out!
I'm not in RabbitMQ mode right now... I might dig into again at some point though... In other words I don't know :)
Can the dead letter messages in the dead letter queue requeue back to the origian queue ?
Yes easily. Setup a timeout
Or manually "shovel" the messages to the original queue.
@@MikesTechCorner I setup time to live to the dead letter queue but it doesn't work
@@MikesTechCorner So I have to bind dead letter queue to another exchange and bind that exchange to original queue, but I don't know whether it is a good way
@@naoko1927 Or you setup a timeout on the dlq and another dlq exchange which could be the original exchange