8373877: QUIC connections are removed too early#28874
8373877: QUIC connections are removed too early#28874djelinski wants to merge 2 commits intoopenjdk:masterfrom
Conversation
|
👋 Welcome back djelinski! A progress list of the required criteria for merging this PR into |
|
@djelinski This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be: You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 3 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ To integrate this PR with the above commit message to the |
|
@djelinski The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
dfuch
left a comment
There was a problem hiding this comment.
Looks good to me. We now only enter draining when we receive ConnectionCloseFrame, if we haven't sent ConnectionCloseFrame already.
If we are already in draining state, nothing to do.
If we are already in closing state, then we stay in closing state.
Looks good.
|
Thanks @dfuch for the review. /integrate |
|
Going to push as commit 7a7e7c9.
Your commit was automatically rebased without conflicts. |
|
@djelinski Pushed as commit 7a7e7c9. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
When a QUIC connection receives a CONNECTION_CLOSE frame, it is supposed to enter the draining state, where all incoming (reordered / replayed) packets are silently discarded. However, the current implementation removes the connection from the endpoint, and reordered/replayed packets trigger sending of a stateless reset instead. This patch fixes that issue.
I modified the
StatelessResetReceiptTestto verify that the connection is still registered with the endpoint after it enters the draining state. The new test fails (most of the time) without the fix, passes with the fix.Existing httpclient tests continue to pass.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/28874/head:pull/28874$ git checkout pull/28874Update a local copy of the PR:
$ git checkout pull/28874$ git pull https://git.openjdk.org/jdk.git pull/28874/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 28874View PR using the GUI difftool:
$ git pr show -t 28874Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/28874.diff
Using Webrev
Link to Webrev Comment