-
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
Jetty-12 already complete exception #8211
Labels
Bug
For general bugs on Jetty side
Comments
@sbordet , @lorban, @lachlan-roberts, @gregw can one of us investigate this |
lachlan-roberts
added a commit
that referenced
this issue
Jun 28, 2022
Signed-off-by: Lachlan Roberts <[email protected]>
lachlan-roberts
added a commit
that referenced
this issue
Jul 4, 2022
Signed-off-by: Lachlan Roberts <[email protected]>
sbordet
added a commit
that referenced
this issue
Aug 4, 2022
…#8215) Now all the logic for completion is in lockedOnComplete(). Avoid throwing in ChannelCallback.succeeded() if HttpChannelState._error != null. This is necessary because HttpChannelState._error may be set asynchronously by some event such as HTTP/2 reset streams or idle timeouts, but if there is a thread dispatched to the application the asynchronous event will not fail the callback, as the failure may be noticed by the application (e.g. via a read() call). Fixed TrailersTest.testHandlerRequestTrailers() by avoid reading again after having read the trailers. Signed-off-by: Lachlan Roberts <[email protected]> Signed-off-by: Simone Bordet <[email protected]> Co-authored-by: Simone Bordet <[email protected]>
PR #9090 is the last thing keeping this issue open. |
github-project-automation
bot
moved this from 🏗 In progress
to ✅ Done
in Jetty 12.0.0.beta0 - FROZEN
Feb 2, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Jetty version(s)
jetty-12
Java version/vendor
(use: java -version)
OS type/version
Description
When building with tests, the following exception is produced many times from many tests. This should either not happen, or if it is normal (??) then the log should be stackless at least.
The text was updated successfully, but these errors were encountered: