-
Notifications
You must be signed in to change notification settings - Fork 632
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 at HttpClientOperations.isWebsocket #342
Comments
@lhotari just to clarify that we need to disable the pool in order to reproduce the issue. Is that correct? |
@violetagg yes, that's the case. |
@violetagg I tested with the |
@violetagg yes, that fixed the NPE. Thank you |
…uest, force the channel close As the onHandlerTerminate will be invoked and it will remove the ChannelOperations from the channel attributes, when the onOutboundComplete is invoked while checking for websocket the implementation needs to take into account that the ChannelOperations might be removed already. This is related to issue #342
fixed by 4a2e773 thanks for testing |
Expected behavior
Calling
HttpClientOperations.isWebsocket
shouldn't throw a NPE.Actual behavior
NPE gets thrown in some cases:
Steps to reproduce
Reproducing the issue might be hard. I did this to get the error, the error appeared in the gateway logs:
I was able to reproduce the issue twice. On the first time, it took about 2 minutes to reproduce and on the second time, it took over 7 minutes to reproduce.
Reactor Netty version
0.7.7.BUILD-SNAPSHOT (ac103c0)
JVM version (e.g.
java -version
)OS version (e.g.
uname -a
)Linux 4.13.0-39-generic #44~16.04.1-Ubuntu
The text was updated successfully, but these errors were encountered: