8375999: com/sun/jndi/ldap/LdapPoolTimeoutTest.java fails sporadically on Windows

[rm-gh-8]

Backporting JDK-8375999: com/sun/jndi/ldap/LdapPoolTimeoutTest.java fails sporadically on Windows.

This PR fixes sporadic LdapPoolTimeoutTest.java failures on Windows by restoring a Windows-specific exception message that was accidentally removed in https://bugs.openjdk.org/browse/JDK-8287062, which in turn was added for parity with Oracle JDK. Already backported to 25.

Ran related tests on linux-x64, linux-aarch64, macos-aarch64 and windows-x64:

make test TEST=test/jdk/com/sun/jndi/ldap/LdapPoolTimeoutTest.java

Results attached:

windows-x64-specific-test.log
macos-aarch64-specific-test.log
linux-x64-specific-test.log
linux-aarch64-specific-test.log

---

Progress

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

Issue

• JDK-8375999: com/sun/jndi/ldap/LdapPoolTimeoutTest.java fails sporadically on Windows (Bug - P5 - Approved)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 2635

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

Using diff file

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

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back rm-gh-8! A progress list of the required criteria for merging this PR into pr/2625 will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@rm-gh-8 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:

8375999: com/sun/jndi/ldap/LdapPoolTimeoutTest.java fails sporadically on Windows

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:

• 818dd7f: 8378218: MSYS2 reports cygwin triplet causing bash configure failure
• 9945500: 8377905: gcc.md included with every build

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

[openjdk]

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

[mlbridge]

Webrevs

• 02: Full - Incremental (449a69cf)
• 01: Full - Incremental (73f7faad)
• 00: Full (73f7faad)

[rm-gh-8]

/approval request for backport of JDK-8375999: com/sun/jndi/ldap/LdapPoolTimeoutTest.java fails sporadically on Windows.

This is a test fix that addresses an issue caused by https://bugs.openjdk.org/browse/JDK-8287062, which in turn was added for parity with Oracle JDK. Already backported to 25.

[openjdk]

@rm-gh-8
8375999: The approval request has been created successfully.

[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 JDK-8375999-V21
git fetch https://git.openjdk.org/jdk21u-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

[rm-gh-8]

/integrate

[openjdk]

@rm-gh-8
Your change (at version 449a69c) is now ready to be sponsored by a Committer.

[phohensee]

/sponsor

[openjdk]

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

• 746ad88: 8378853: [25u] Make backport of JDK-8244336 comply with differences in CSR
• 2410cdb: 8377526: Update Libpng to 1.6.55
• 818dd7f: 8378218: MSYS2 reports cygwin triplet causing bash configure failure
• ... and 1 more: https://git.openjdk.org/jdk21u-dev/compare/0643296564d39c9500164c4232d754f3a5f46f04...master

Your commit was automatically rebased without conflicts.

[openjdk]

@phohensee @rm-gh-8 Pushed as commit 0cd2d9b.

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