Fixes #12553 - Execute immediately HTTP/2 failures. #12557
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Now idle timeouts and failures are executed immediately for HTTP/2 and HTTP/3, rather than feeding them to the execution strategy, where they may be queued and never run. Signed-off-by: Simone Bordet <[email protected]>
sbordet
added
the
Sponsored
gregw
previously approved these changes
Nov 21, 2024
Contributor
gregw
left a comment
gregw
left a comment
There was a problem hiding this comment.
Looks good... one small suggestion.
jetty-core/jetty-util/src/main/java/org/eclipse/jetty/util/thread/ThreadPool.java
Outdated
Show resolved
Hide resolved
Signed-off-by: Simone Bordet <[email protected]>
lorban
approved these changes
Nov 22, 2024
sbordet
deleted the
fix/jetty-12.0.x/12553/execute-failures-immediately
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Now idle timeouts and failures are executed immediately for HTTP/2 and HTTP/3, rather than feeding them to the execution strategy, where they may be queued and never run.