-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Http2Exception: Flow control window exceeded for stream: 0 when sending a ~64 KiB attachment #4814
Comments
Do you know if the connection is using TLS? (h2 vs h2c) |
The test does not set any certs on the server side. That implies h2c, I guess? |
sounds like #4802 |
It's what I was thinking too (so my question about h2c). However, the stack trace is very different and the fact that it was working before may indicate it's something else. |
Thanks for the suggestion, @vietj! I have cherry-picked 322d095 on top of 4.4.4, I have rebuilt vert.x and then I re-run the test. The soak test failed much later on round 2205 and the error message is fully different:
|
the issue does not clearly indicates the problem you should look at the JVM dump |
The |
Yes, the issue with the limits is definitely different from the one reported initially. I need to investigate it further. |
Version
Reproducible on Vert.x Core 4.4.4 (Quarkus 3.3.0, 3.2.4), Vert.x Core 4.4.2 (Quarkus 3.1), Vert.x Core 4.4.1 (Quarkus 3.0)
It works on the following versions: Core 4.3.7 (Quarkus 2.16)
Context
There are two slightly different ways to reproduce the issue. Both are present in quarkiverse/quarkus-cxf#974
In both cases, the stack trace (on the server side) is the following:
Some observations:
quarkus.http.http2=false
on the server causes a slightly different exception on a different place in netty code, hence HTTP/1 does not work either.quarkus.http.limits.max-body-size
does not change anythingDo you have a reproducer?
A reproducer is a simple project hosted on GitHub (or another forge supporting git clone operation) that has a build file that can be executed to reproduce the issue.
Reproducers are very helpful for contributors and will likely help them fixing your bug faster.
Steps to reproduce
The text was updated successfully, but these errors were encountered: