-
-
Notifications
You must be signed in to change notification settings - Fork 15.8k
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
NPE while trying to invoke the method HttpMethod.name() #9459
Milestone
Comments
normanmaurer
added a commit
that referenced
this issue
Aug 14, 2019
Motivation: It was possible to produce a NPE when we for examples received more responses as requests as we did not check if the queue did not contain a method before trying to compare method names. Modifications: - Add extra null check - Add unit tet Result: Fixes #9459
Big thanks for the fix @normanmaurer! |
normanmaurer
added a commit
that referenced
this issue
Aug 16, 2019
Motivation: It was possible to produce a NPE when we for examples received more responses as requests as we did not check if the queue did not contain a method before trying to compare method names. Modifications: - Add extra null check - Add unit tet Result: Fixes #9459
normanmaurer
added a commit
that referenced
this issue
Aug 16, 2019
Motivation: It was possible to produce a NPE when we for examples received more responses as requests as we did not check if the queue did not contain a method before trying to compare method names. Modifications: - Add extra null check - Add unit tet Result: Fixes #9459
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I'm using the Netty client through Reactor Netty and the Cloud Foundry Java client in order to communicate with a Cloud Foundry controller. Usually everything works fine, but sometimes I get the following
NullPointerException
:The exception occurs on different requests and it's also not that easily reproducible - 3 occurrences in 20000 HTTP requests.
Steps to reproduce
N/A. My hope is that you'll know the issue when you see the stack trace.
Minimal yet complete reproducer code (or URL to code)
I don't have a unit test that reproduces the issue ATM. If you need one, I'll try to write something.
Netty version
Reactor Netty 0.8.10.RELEASE + Netty 4.1.29.Final
JVM version (e.g.
java -version
)java version "1.8.0_212"
Java(TM) SE Runtime Environment (build 8.1.055)
OS version (e.g.
uname -a
)Linux 4f05ab19-01cd-458d-6c4f-93d3 4.15.0-55-generic #60~16.04.2-Ubuntu SMP Thu Jul 4 09:03:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
The text was updated successfully, but these errors were encountered: