-
Notifications
You must be signed in to change notification settings - Fork 38.3k
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
Fixing NPE in AbstractNamedValueMethodArgumentResolver #23882
Conversation
@dekelpilli Please sign the Contributor License Agreement! Click here to manually synchronize the status of this Pull Request. See the FAQ for frequently asked questions. |
@dekelpilli Thank you for signing the Contributor License Agreement! |
@dekelpilli, I can make this more lenient again to avoid a NPE but it does mean that some code somewhere is creating the argument resolver by passing |
@rstoyanchev Sure, I'll try to do that at work tomorrow. The problem is that the stacktrace is from when the exception is thrown, not when the resolver is built. I'll try to run it locally with a breakpoint and provide that as well. |
Right, I would only use the stacktrace as a clue. If you can point me to the code that's creating the resolver that would be quite sufficient. |
Creation stacktrace (this is from a test running locally, but the issue first appeared in a live dev server):
Exception stacktrace:
|
Thanks, it's right here where the header resolver is created. I've processed the change to fall back on a default |
Upgrading one of our apps to Spring Boot 2.2.0.RELEASE (with Spring 5.2.0.RELEASE) is blocked by a null pointer exception in AbstractNamedValueMethodArgumentResolver that occurs whenever we are trying to receive a message via an
SqsListener
.My approach is to undo 5b3b0b1#diff-ba4bc09499d8cbf059d24ea9c6062b9cL82