[
https://issues.apache.org/jira/browse/CAMEL-23907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18123623#comment-18123623
]
Guillaume Nodet commented on CAMEL-23907:
-----------------------------------------
This issue appears to have been already fixed on the main branch in commit
d5b4dba33e19aca84ec21bef8ba99fa2cdcaf77f (PR #24423, merged July 6, 2026).
The fix replaced fixed-timeout assertions with Awaitility-based polling in
testThreadsRejectedAbortNoRedelivery and sibling test methods, eliminating the
timing sensitivity that caused failures on JDK 25.
Please verify and close if confirmed.
_Note: This comment was generated by an AI coding agent and requires manual
verification._
> Flaky test: ThreadsRejectedExecutionTest in camel-core
> ------------------------------------------------------
>
> Key: CAMEL-23907
> URL: https://issues.apache.org/jira/browse/CAMEL-23907
> Project: Camel
> Issue Type: Test
> Components: camel-core
> Reporter: Guillaume Nodet
> Assignee: Guillaume Nodet
> Priority: Major
> Labels: flaky-test
> Fix For: 4.22.0
>
>
> The test `ThreadsRejectedExecutionTest.testThreadsRejectedAbortNoRedelivery`
> in `camel-core` is flaky in CI.
> Observed failure on JDK 25 in PR #24358 CI run (July 4, 2025). This test
> involves thread pool rejection with abort policy, which is timing-sensitive.
> The test should be stabilized, potentially using Awaitility instead of any
> timing-dependent assertions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
