8273831: PrintServiceLookup spawns 2 threads in the current classloader, getting orphaned

[mrserb]

Hi all,

This pull request contains a backport of commit 68756782 from the openjdk/jdk repository.

The commit being backported was authored by Sergey Bylokhov on 30 Oct 2021 and was reviewed by Alexey Ivanov.

Thanks!

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• JDK-8273831 needs maintainer approval

Issue

• JDK-8273831: PrintServiceLookup spawns 2 threads in the current classloader, getting orphaned (Bug - P4 - Approved)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev.git pull/1625/head:pull/1625
$ git checkout pull/1625

Update a local copy of the PR:
$ git checkout pull/1625
$ git pull https://git.openjdk.org/jdk17u-dev.git pull/1625/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 1625

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/1625.diff

Webrev

Link to Webrev Comment

[bridgekeeper]

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

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

8273831: PrintServiceLookup spawns 2 threads in the current classloader, getting orphaned

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.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[mlbridge]

Webrevs

• 02: Full - Incremental (e50dffb0)
• 01: Full - Incremental (ea6da0d0)
• 00: Full (0bd4c38c)

[openjdk]

⚠️ @mrserb This change is now ready for you to apply for maintainer approval. This can be done directly in each associated issue or by using the /approval command.

[GoeLin]

Hi @mrserb, what keeps you from integrating this? It's ready to go. But maybe you want to merge head to rerun the tests before integrating to account for the changes that were done in the meantime. The same holds for follow-up 8276819.

[mrserb]

/integrate

[openjdk]

Going to push as commit 5cb86e3.

[openjdk]

@mrserb Pushed as commit 5cb86e3.

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