-
Notifications
You must be signed in to change notification settings - Fork 646
AMQP-200: Listener Exceptions Should be Logged at at Least WARN level #15
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should not log under warn after testing for isInfoEnabled (or isDebugEnabled). Always log at the same level as if test.
simply replace both with a single
if (logger.isWarnEnabled() {
logger.warn(...., ex);
}
(See JMS AMLC)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. Just updated the commit range.
|
James, Before we go any further, have you reviewed and signed the Individual Contributor Agreement? https://support.springsource.com/spring_committer_signup Thanks |
|
Yes. I did when I contributed some changes last year.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great!
You should remove this last else if{...} stanza; it will never be executed because the one above it will run.
Thanks.
|
Changes made |
|
Mark, LGTM - ok to merge (w/ squash). |
Commits speak for themselves. Low hanging fruit that I thought I'd take since I got bit by this very issue today.