-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
GET requests trigger NullPointerExceptions #10364
Comments
A downgrade to v1.47.1 fixes the problem. This seems to be a regression introduced with the netty upgrade(#9451) in v1.50.0. Tested via v1.47.1:
v1.50.0:
|
It seems like v1.50.0 and onwards is having problems with the The problem seems to be that |
@ejona86 this seems to be a regression introduced by #9177 ? 4b57d40#diff-f125363f032a4f7b2dac63ed5078f8768c82743cd102544f2d34f8507da2be0cR858-R860 |
Fixes grpc#10364
* Eliminate NPE by skipping further processing when stream is defined, but doesn't have a property for streamKey (header processing identified an error) Fixes #10364 * Add unit test for missing content type
Yeah, I think so. But that change also fixed the same method for gRPC traffic, so overall it was probably still an improvement. And the log-spam has been a long-lived occurrence when the client sent the request in two frames instead of one, which is permitted even for GET and we have seen. |
* Eliminate NPE by skipping further processing when stream is defined, but doesn't have a property for streamKey (header processing identified an error) Fixes grpc#10364 * Add unit test for missing content type
What version of gRPC-Java are you using?
1.56.1
What is your environment?
Docker container based on Ubuntu 22.04 with OpenJDK 17
What did you expect to see?
No NPE. gRPC should gracefully handle any non-gRPC clients without spamming the log. In our case this is triggered by an active healtcheck from our loadbalancer.
What did you see instead?
Steps to reproduce the bug
The text was updated successfully, but these errors were encountered: