8274524: SSLSocket.close() hangs if it is called during the ssl handshake

[pkumaraswamy]

This is a clean backport.
The fix has been confirmed by running against internal test suite and JCK SSL tests, where the initial failure was observed in test api/javax_net/ssl/SSLSocket/setUseClientMode.html

---

Progress

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

Issue

• JDK-8274524: SSLSocket.close() hangs if it is called during the ssl handshake

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk18u pull/33/head:pull/33
$ git checkout pull/33

Update a local copy of the PR:
$ git checkout pull/33
$ git pull https://git.openjdk.java.net/jdk18u pull/33/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 33

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk18u/pull/33.diff

[bridgekeeper]

👋 Welcome back pkumaraswamy! 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.

[openjdk]

@pkumaraswamy 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:

8274524: SSLSocket.close() hangs if it is called during the ssl handshake

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 no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential 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.

➡️ 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).

[mlbridge]

Webrevs

• 00: Full (daf1548c)

[pkumaraswamy]

/integrate

[openjdk]

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

[coffeys]

/sponsor

[openjdk]

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

• 9bd2fc6: 8281093: Violating Attribute-Value Normalization in the XML specification 1.0
• 16ff056: 8276990: Memory leak in invoker.c fillInvokeRequest() during JDI operations
• 32c0aa2: 8278186: org.jcp.xml.dsig.internal.dom.Utils.parseIdFromSameDocumentURI throws StringIndexOutOfBoundsException when calling substring method

Your commit was automatically rebased without conflicts.

[openjdk]

@coffeys @pkumaraswamy Pushed as commit afae492.

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