[
https://issues.apache.org/jira/browse/CAMEL-25260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18125059#comment-18125059
]
Guillaume Nodet commented on CAMEL-25260:
-----------------------------------------
This issue is being investigated by a coding agent (on behalf of gnodet).
Investigation findings:
- Confirmed: no executor-service setting in the JUnit parallel config
(parent/pom.xml surefire configurationParameters, components/pom.xml failsafe
block)
- The warning fires for all ~39 modules with camel.surefire.parallel=true or
camel.failsafe.parallel=true
- Two options: (1) set executor-service=FORK_JOIN_POOL to silence the warning
while keeping current behaviour; (2) switch to WORKER_THREAD_POOL (still
experimental in JUnit 6.x)
- Caution for option 2: CamelParallelExecutionStrategy in camel-core uses
ForkJoinPool.getSaturatePredicate() API which is ForkJoinPool-specific and
would not be invoked with WORKER_THREAD_POOL
- Recommended approach: start with FORK_JOIN_POOL to silence warning; benchmark
WORKER_THREAD_POOL separately
_Note: This comment was generated by an AI coding agent and requires manual
verification._
> Try
> junit.jupiter.execution.parallel.config.executor-service=WORKER_THREAD_POOL
> -------------------------------------------------------------------------------
>
> Key: CAMEL-25260
> URL: https://issues.apache.org/jira/browse/CAMEL-25260
> Project: Camel
> Issue Type: Test
> Components: build system
> Affects Versions: 4.23.0
> Reporter: Aurélien Pupier
> Assignee: Guillaume Nodet
> Priority: Major
>
> in logs, there are many times:
> {noformat}
> [INFO] Parallel test execution is enabled but the default ForkJoinPool-based
> executor service will be used. Please give the new implementation based on a
> regular thread pool a try by setting the
> 'junit.jupiter.execution.parallel.config.executor-service' configuration
> parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team.
> Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide
> this message and keep using the original implementation.
> {noformat}
> could be worthy to give a try to see if there are improvements (maybe also
> with the other work in progress with -T1C)
> either it is better and use it, or not better and set
> junit.jupiter.execution.parallel.config.executor-service=FORK_JOIN_POOL to
> avoid the thousands of messages in the log
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
