Repository navigation
HttpDistTest.maxQueuedRequestsTest fails on runners with limited vCPUs #48598
Description
Before reporting an issue
- I have read and understood the above terms for submitting issues, and I understand that my issue may be closed without action if I do not follow them.
Area
ci
Describe the bug
HttpDistTest.maxQueuedRequestsTest fails on slower machines. The test fires 5 HTTP requests intended to be concurrent, but uses CompletableFuture.supplyAsync() without an explicit executor. Without it it seems to default to ForkJoinPool.commonPool(), which thread count depends on available CPUs - Math.max(1, availableProcessors() - 1). On runners with limited vCPUs the pool has only 1 thread, so requests are sent one at a time instead of concurrently. The server handles each request before the next arrives, the queue never fills (returns 204 instead of 503).
The test was introduced with #24684.
Version
nightly
Regression
- The issue is a regression
Expected behavior
At least one of the 5 requests should be rejected with 503, because the --http-pool-max-threads=1 --http-max-queued-requests=1 properties.
Actual behavior
All 5 requests return 204. Logs confirm sequential handling on a single thread, ~5s apart:
11:47:49,492 Sleeping for 5000 millis
11:47:54,492 Waking up...
11:47:54,505 Sleeping for 5000 millis
11:47:59,505 Waking up...
...
https://github.com/keycloak/keycloak-private/actions/runs/25105361344/job/73567071490?pr=602#logs
How to Reproduce?
Run the test on a machine with limited vCPUs (e.g., 2), or force low parallelism:
-Djava.util.concurrent.ForkJoinPool.common.parallelism=1
Anything else?
No response
Activity
HttpDistTest.maxQueuedRequestsTest fails on runners with limited vCPUs (
Quarkus test fixes (#606)
HttpDistTest.maxQueuedRequestsTest fails on runners with limited vCPUs (