gnodet opened a new pull request, #26181: URL: https://github.com/apache/camel/pull/26181
## Problem `JmsConcurrentConsumerInOnlyTest.testConcurrentConsumers` is flaky — it has failed 13 times in 90 days, always on s390x. The test sends 2000 messages to a JMS queue through concurrent consumers (2-5) with random 0-10ms delays per message, then calls `MockEndpoint.assertIsSatisfied(context)` with no explicit timeout. This falls back to the default 10-second `waitForCompleteLatch`, which is insufficient on slow architectures (s390x, aarch64) or under CI load. ## Fix Replace `MockEndpoint.assertIsSatisfied(context)` with `MockEndpoint.assertIsSatisfied(context, 30, TimeUnit.SECONDS)` to use an explicit 30-second timeout. This is consistent with `JmsDefaultTaskExecutorTypeTest` in the same module, which already uses `MockEndpoint.assertIsSatisfied(context, 40, TimeUnit.SECONDS)`. JIRA: https://issues.apache.org/jira/browse/CAMEL-24600 _AI agent (Hermes on behalf of gnodet)_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
