8273026: Slow LoginContext.login() on multi threading application

[Larry-N]

Backport the fix 8273026. Applied with conflicts, tested by tier2.

---

Progress

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

Issue

• JDK-8273026: Slow LoginContext.login() on multi threading application

Reviewers

• Yuri Nesterenko (@yan-too - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 141

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

Using diff file

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

[bridgekeeper]

👋 Welcome back Larry-N! 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 (7943423b)

[openjdk]

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

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

8273026: Slow LoginContext.login() on multi threading application

Reviewed-by: yan

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:

• c361e15: 8250894: Provide a configure option to build and run against the platform libharfbuzz
• e6d8cfc: 8250605: Linux x86_32 builds fail after JDK-8249821
• 5bc3e18: 8249821: Separate libharfbuzz from libfontmanager

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 (@yan-too) 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).

[Larry-N]

/integrate

[openjdk]

@Larry-N
Your change (at version 7943423) is now ready to be sponsored by a Committer.

[yan-too]

/sponsor

[openjdk]

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

• c361e15: 8250894: Provide a configure option to build and run against the platform libharfbuzz
• e6d8cfc: 8250605: Linux x86_32 builds fail after JDK-8249821
• 5bc3e18: 8249821: Separate libharfbuzz from libfontmanager

Your commit was automatically rebased without conflicts.

[openjdk]

@yan-too @Larry-N Pushed as commit 408901d.

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