8211227: Inconsistent TLS protocol version in debug output

[evwhelan]

Hi,

Please review my backport of JDK-8211227

All testing passed.

Regards,
Evan

---

Progress

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

Issue

• JDK-8211227: Inconsistent TLS protocol version in debug output

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 126

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

Using diff file

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

[bridgekeeper]

👋 Welcome back ewhelan! 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]

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

8211227: Inconsistent TLS protocol version in debug output

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 2 new commits pushed to the master branch:

• 375be17: 8264786: [macos] All Swing/AWT apps cause Allow Notifications prompt to appear when app is launched
• 6f948a7: 8267842: SIGSEGV in get_current_contended_monitor

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.

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

[evwhelan]

/integrate

[openjdk]

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

[mlbridge]

Webrevs

• 00: Full (f4333c1a)

[RealCLanger]

/sponsor

[openjdk]

@RealCLanger @evwhelan Since your change was applied there have been 2 commits pushed to the master branch:

• 375be17: 8264786: [macos] All Swing/AWT apps cause Allow Notifications prompt to appear when app is launched
• 6f948a7: 8267842: SIGSEGV in get_current_contended_monitor

Your commit was automatically rebased without conflicts.

Pushed as commit 7616b2c.

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