-
Notifications
You must be signed in to change notification settings - Fork 1.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
NPE in ResponseListeners content notification #10726
Comments
…he original source spuriously calls demand() Signed-off-by: Ludovic Orban <lorban@bitronix.be>
Signed-off-by: Ludovic Orban <lorban@bitronix.be>
* #10726 fix NPE in ResponseListeners when demultiplexing is used and the original source spuriously calls demand() Signed-off-by: Ludovic Orban <lorban@bitronix.be>
Hi again, the problem does not seem completely fixed, jetty 12.0.3 fails with
I've got java 17 application running inside docker container and performing some requests to maven-central. If this same application is running locally (not inside container), no problems occur. |
@olenagerasimova This seems to be caused by a different problem. I tried running the reproducer you included in jetty-project/jetty-reactive-httpclient#296 and it passes with You should open a new jetty-reactive-httpclient issue with a new reproducer if possible. Thanks! |
Jetty version(s)
12+
Description
Reported in jetty-project/jetty-reactive-httpclient#296.
This probably happens with
Transfer-Encoding: chunked
, when there is data to read, but it is only the chunk metadata, as in:In this case, there will be a wakeup of the demand callback because there is data, but calling
response.read()
would yieldnull
.This case is not covered in the case of multiple response listeners in
ResponseListeners
.The text was updated successfully, but these errors were encountered: