RFR: 8367983: javax/management/monitor/ThreadPoolTest.java and StartStopTest.java fail with Unexpected Maximum Pool Size Overflow!

Kevin Walls kevinw at openjdk.org
Thu Sep 18 12:17:56 UTC 2025


This test has failed due to a timing issue, but not continually or reproducibly.
Looks like an effect of the TIMEOUT_FACTOR change (8260555).

The recent failure has -J-Dtest.timeout.factor=1.0 and I see older logs passing with -Dtest.timeout.factor=4.0

We should increase the timeout.  As there have been occasional failures before, looking back a few years, so multiply the current 500ms by a little more than 4.ack a few years, so multiply the current 500ms by a little more than 4.

-------------

Commit messages:
 - 8038950: javax/management/monitor/ThreadPoolTest.java and StartStopTest.java fail with Unexpected Maximum Pool Size Overflow!

Changes: https://git.openjdk.org/jdk/pull/27361/files
  Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=27361&range=00
  Issue: https://bugs.openjdk.org/browse/JDK-8367983
  Stats: 5 lines in 1 file changed: 2 ins; 0 del; 3 mod
  Patch: https://git.openjdk.org/jdk/pull/27361.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/27361/head:pull/27361

PR: https://git.openjdk.org/jdk/pull/27361


More information about the serviceability-dev mailing list