gnodet commented on PR #25292: URL: https://github.com/apache/camel/pull/25292#issuecomment-5163729280
## ❌ Local IT results for `7d28291fc2353bc2955c22ffefa9e6fa9f29e133` Integration test failures detected — **IBM MQ 10.0.0.0-r3 container takes longer to accept JMS connections**, exceeding the 30-second timeout in `IbmMQLocalContainerInfraService`. **Test-infra module**: `camel-test-infra-ibmmq` **Components tested**: `components/camel-jms` ### Test Results Summary | Metric | Count | |--------|-------| | Total tests | 439 | | Passed | 428 | | Failed (errors) | 2 | | Skipped | 9 | ### Failures Both failures are in `@beforeAll` — the container starts but the JMS service inside takes >30s to become ready: 1. **`JmsComponentIbmMQTest`** — `ConditionTimeout`: Condition 'IBM MQ accepting JMS connections' didn't complete within 30 seconds 2. **`JmsReplyToIbmMQTest`** — Same timeout error Each test was retried 3 times with the same result — this is not a flake. ### Root Cause The Awaitility timeout in [`IbmMQLocalContainerInfraService.waitForJmsConnection()`](https://github.com/apache/camel/blob/main/test-infra/camel-test-infra-ibmmq/src/main/java/org/apache/camel/test/infra/ibmmq/services/IbmMQLocalContainerInfraService.java#L109-L121) is set to 30 seconds. The new IBM MQ 10.0.0.0-r3 container takes longer to initialize its JMS listener. ### Suggested Fix Increase the Awaitility timeout from 30 seconds to 120 seconds in `IbmMQLocalContainerInfraService.java`: ```java Awaitility.await("IBM MQ accepting JMS connections") .atMost(120, TimeUnit.SECONDS) // was 30 — IBM MQ 10.x needs more startup time .pollInterval(1, TimeUnit.SECONDS) ``` > _Local integration tests run by ForgeBot on behalf of @gnodet_ > _Tests run without `-Dci.env.name` to include ITs disabled on GitHub Actions CI_ -- 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]
