-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
8274736: Concurrent read/close of SSLSockets causes SSLSessions to be invalidated unnecessarily #6197
Conversation
👋 Welcome back jnimeh! A progress list of the required criteria for merging this PR into |
Webrevs
|
@jnimeh 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 302 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
…without using session tickets
/* | ||
* @test | ||
* @bug 8274736 | ||
* @summary Concurrent read/close of SSLSockets causes SSLSessions to be invalidated unnecessarily |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor nit. Can you keep these under 80 chars?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No problem.
/integrate |
Going to push as commit 8822d41.
Your commit was automatically rebased without conflicts. |
This fix handles cases where two or more threads may be acting on a single SSLSocket instance. In cases where one thread closes the socket while the other is in the middle of a read, a SocketException is appropriately thrown, but it results in SSLSession invalidation even though the session was legitimately negotiated at an earlier point in time and should remain in the cache.
JBS: https://bugs.openjdk.java.net/browse/JDK-8274736
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/6197/head:pull/6197
$ git checkout pull/6197
Update a local copy of the PR:
$ git checkout pull/6197
$ git pull https://git.openjdk.java.net/jdk pull/6197/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 6197
View PR using the GUI difftool:
$ git pr show -t 6197
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/6197.diff