-
Notifications
You must be signed in to change notification settings - Fork 39
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
[RabbitMQ] Error policy with RabbitMQ is apparently not working #234
Comments
@BEagle1984 Could I be doing something wrong? |
I've to check this. I'll verify and report back. 👍 |
thank you very much |
Is this a sample project? Would it be possible to share the source code? |
It's a corporate project, it's a nuget package that we built around Silverback, in order to facilitate some configurations, we have a sample api just to validate that everything is ok, I'm going to remove the sensitive parts of the project and put together a poc with just the parts techniques and send them to you, I still send them to you today. |
Just a heads-up that RabbitMQ support will be deprecated in Silverback v5. You can find more details and the reasoning in the discussion here: #237. Contributions are welcome if someone wants to take over maintaining it! |
Error policy with RabbitMQ is apparently not working. I implemented the retry policy with the move after attempts, but I noticed that the failedAttempts is not being incremented when there is an error in the consumer. It stays in an infinite loop because of this. Here are my configurations.
failedAttempts always remains 1 and ends up going into an infinite loop
The text was updated successfully, but these errors were encountered: