Skip to content
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

HTTP/2 connection not closed after idle timeout when TCP congested #11259

Closed
sbordet opened this issue Jan 11, 2024 · 0 comments · Fixed by #11267 or #11269
Closed

HTTP/2 connection not closed after idle timeout when TCP congested #11259

sbordet opened this issue Jan 11, 2024 · 0 comments · Fixed by #11267 or #11269
Assignees
Labels
Bug For general bugs on Jetty side

Comments

@sbordet
Copy link
Contributor

sbordet commented Jan 11, 2024

Jetty version(s)
12+

Jetty Environment
core

Description
See #11256.

@sbordet sbordet added the Bug For general bugs on Jetty side label Jan 11, 2024
@sbordet sbordet changed the title HTTP/2 connection not closed when TCP congested HTTP/2 connection not closed after idle timeout when TCP congested Jan 11, 2024
@sbordet sbordet self-assigned this Jan 11, 2024
sbordet added a commit that referenced this issue Jan 12, 2024
…CP congested.

Now upon the second idle timeout, the connection is forcibly closed.
Fixed also similar problem in HTTP/3.

Signed-off-by: Simone Bordet <simone.bordet@gmail.com>
sbordet added a commit that referenced this issue Jan 15, 2024
…CP congested. (#11267)

Now upon the second idle timeout, the connection is forcibly closed.
Fixed also similar problem in HTTP/3.

Signed-off-by: Simone Bordet <simone.bordet@gmail.com>
sbordet added a commit that referenced this issue Jan 15, 2024
…CP congested. (#11268)

* Backport of #11267.

Signed-off-by: Simone Bordet <simone.bordet@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For general bugs on Jetty side
Projects
No open projects
Status: ✅ Done
1 participant