-
Notifications
You must be signed in to change notification settings - Fork 626
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
Flooding of 'Failed to check/redeclare auto-delete queue(s)' error messages #1477
Milestone
Comments
garyrussell
added
type: improvement
and removed
type: bug
status: waiting-for-triage
labels
Jul 27, 2022
We can remove the stack trace, but I believe that the logs must remain, perhaps at WARN level which would allow you to suppress them. Please note that 2.2.x is no longer supported as OSS https://spring.io/projects/spring-amqp#support |
Thanks for the quick reply. |
garyrussell
added a commit
to garyrussell/spring-amqp
that referenced
this issue
Oct 20, 2022
Resolves spring-projects#1477 Only log the stack trace on the first failure. Tested with a Boot app and stop/start/stop the broker. **cherry-pick to 2.4.x**
artembilan
pushed a commit
that referenced
this issue
Oct 21, 2022
Resolves #1477 Only log the stack trace on the first failure. Tested with a Boot app and stop/start/stop the broker. **cherry-pick to 2.4.x**
artembilan
pushed a commit
that referenced
this issue
Oct 21, 2022
Resolves #1477 Only log the stack trace on the first failure. Tested with a Boot app and stop/start/stop the broker. **cherry-pick to 2.4.x**
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In what version(s) of Spring AMQP are you seeing this issue?
2.2.20 up to latest (probably earlier as well).
Describe the bug
When RabbitMQ service restarts, our log is flooded with error messages when simply trying to recreate queues.
Once RabbitMQ is started again, the queues get re-created correctly and the logging stops.
To Reproduce
Either have
@Bean
declared queues or queues declared viaRabbitAdmin
.Start application
Restart RabbitMQ service
Expected behavior
Do not log error messages when spring AMQP simply is retrying (using configured BackOff polici) to restore declared queues.
Or at least change the log level to info or debug.
When to queues cannot be restored (after number of tries or timeout) an error message is needed.
The text was updated successfully, but these errors were encountered: