8355370: Include server name in HTTP test server thread names to improve diagnostics

[GoeLin]

I backport this for parity with 17.0.17-oracle.

Removed some OpenJDK 21 functionality.
Test using this pass.

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• JDK-8355370 needs maintainer approval
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8355370: Include server name in HTTP test server thread names to improve diagnostics (Enhancement - P4)

Reviewers

• Ralf Schmelter (@schmelter-sap - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 3861

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

Using diff file

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

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back goetz! A progress list of the required criteria for merging this PR into pr/3857 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 change is not yet ready to be integrated.
See the Progress checklist in the description for automated requirements.

[openjdk]

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

[mlbridge]

Webrevs

• 02: Full - Incremental (919fabc5)
• 01: Full (3e096b4e)
• 00: Full (a768de56)

[openjdk]

@GoeLin Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information.

[openjdk-notifier]

The parent pull request that this pull request depends on has now been integrated and the target branch of this pull request has been updated. This means that changes from the dependent pull request can start to show up as belonging to this pull request, which may be confusing for reviewers. To remedy this situation, simply merge the latest changes from the new target branch into this pull request by running commands similar to these in the local repository for your personal fork:

git checkout goetz_backport_8355370
git fetch https://git.openjdk.org/jdk17u-dev.git master
git merge FETCH_HEAD
# if there are conflicts, follow the instructions given by git merge
git commit -m "Merge master"
git push

[openjdk]

⚠️ @GoeLin 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.

[schmelter-sap]

Looks good.