Fix itests on machines with lots of processors (#17263)

When this JVM variable is not set Jetty creates selectors based on the number of available processors (`Runtime.getRuntime().availableProcessors()`).
Jetty will also throw an exception when there is a mismatch between the max thread pool size and the number of selectors.
This causes issues with the default thread pool size of 10 on machines with more than 10 available processors.

See also [`SelectorManager.defaultSelectors(Executor)`](70015831e5/jetty-io/src/main/java/org/eclipse/jetty/io/SelectorManager.java (L71-L80)).

Signed-off-by: Wouter Born <github@maindrain.net>
This commit is contained in:
Wouter Born 2024-08-15 22:37:21 +02:00 committed by GitHub
parent e62f3af4c7
commit fcef4639ca
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -25,7 +25,8 @@ Test-Cases: ${classes;CONCRETE;PUBLIC;NAMED;*Test}
# This property is set by the build-helper-maven-plugin in the itests pom.xml # This property is set by the build-helper-maven-plugin in the itests pom.xml
-runvm: \ -runvm: \
-Djdk.util.zip.disableZip64ExtraFieldValidation=true,\ -Djdk.util.zip.disableZip64ExtraFieldValidation=true,\
-Dorg.osgi.service.http.port=${org.osgi.service.http.port} -Dorg.osgi.service.http.port=${org.osgi.service.http.port},\
-DJETTY_AVAILABLE_PROCESSORS=4
# The integration test itself does not export anything. # The integration test itself does not export anything.
Export-Package: Export-Package: