8268965: TCP Connection Reset when connecting simple socket to SSL server

[alexeybakhtin]

The original patch applies almost clean except of instanceof pattern matching not available in jdk11
The fix is identical to jdk13 patch
sun/security/ssl and new test are passed

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• Change must be properly reviewed

Issue

• JDK-8268965: TCP Connection Reset when connecting simple socket to SSL server

Reviewers

• Martin Doerr (@TheRealMDoerr - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk11u-dev pull/151/head:pull/151
$ git checkout pull/151

Update a local copy of the PR:
$ git checkout pull/151
$ git pull https://git.openjdk.java.net/jdk11u-dev pull/151/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 151

View PR using the GUI difftool:
$ git pr show -t 151

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk11u-dev/pull/151.diff

[bridgekeeper]

👋 Welcome back abakhtin! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

This backport pull request has now been updated with issue from the original commit.

[mlbridge]

Webrevs

• 00: Full (b143ea37)

[TheRealMDoerr]

LGTM. Thanks for backporting!

[openjdk]

@alexeybakhtin This change now passes all automated pre-integration checks.

After integration, the commit message for the final commit will be:

8268965: TCP Connection Reset when connecting simple socket to SSL server

Reviewed-by: mdoerr

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 master branch:

• d78e2be: 8227738: jvmti/DataDumpRequest/datadumpreq001 failed due to "exit code is 134"
• 8637f65: 8227815: Minimal VM: set_state is not a member of AttachListener
• f3098c4: 8225690: Multiple AttachListener threads can be created

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
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.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@TheRealMDoerr) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[alexeybakhtin]

/integrate

[openjdk]

@alexeybakhtin
Your change (at version b143ea3) is now ready to be sponsored by a Committer.

[VladimirKempik]

/sponsor

[openjdk]

Going to push as commit 7501084.
Since your change was applied there have been 3 commits pushed to the master branch:

• d78e2be: 8227738: jvmti/DataDumpRequest/datadumpreq001 failed due to "exit code is 134"
• 8637f65: 8227815: Minimal VM: set_state is not a member of AttachListener
• f3098c4: 8225690: Multiple AttachListener threads can be created

Your commit was automatically rebased without conflicts.

[openjdk]

@VladimirKempik @alexeybakhtin Pushed as commit 7501084.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.