8373086: Make isexceeded001.java more robust

[sendaoYan]

Hi all,

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

The commit being backported was authored by Albert Mingkun Yang on 5 Dec 2025 and was reviewed by Joel Sikström and Thomas Schatzl.

Thanks!

---

Progress

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

Issue

• JDK-8373086: Make isexceeded001.java more robust (Bug - P4)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 69

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

Using diff file

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

Using Webrev

Link to Webrev Comment

[bridgekeeper]

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

• 00: Full (e7f96144)

[jsikstro]

Just a comment. It's nice that the test is now more robust and as a standalone fix this is fine.

However, we don't expect this to fail in JDK 25, since InitialRAMPercentage is 1.5625 by default in this version. The fix in mainline is necessary since we changed InitialRAMPercentage to 0, making this test fail intermittently because the JVM starts with a really small initial heap.

[sendaoYan]

Just a comment. It's nice that the test is now more robust and as a standalone fix this is fine.

However, we don't expect this to fail in JDK 25, since InitialRAMPercentage is 1.5625 by default in this version. The fix in mainline is necessary since we changed InitialRAMPercentage to 0, making this test fail intermittently because the JVM starts with a really small initial heap.

Yes, test vmTestbase/nsk/monitoring/MemoryPoolMBean/isUsageThresholdExceeded/isexceeded00[1-5]/TestDescription.java was not problemlisted in jdk25u-dev. Sorry for the interrupt.