gnodet-bot commented on PR #28012:
URL: https://github.com/apache/camel/pull/28012#issuecomment-6235381269
## ⚠️ Local IT results for `4dbfa551`
The IBM MQ integration tests could not complete due to a **Docker networking
limitation** in the CI environment (Docker-in-Docker). This is an environment
constraint, not a regression introduced by the `10.0.0.0-r4 → 10.0.1.0-r1`
upgrade.
**Test-infra module**: `camel-test-infra-ibmmq`
**Component tested**: `camel-jms`
**Docker image**: `icr.io/ibm-messaging/mq:10.0.1.0-r1`
| Suite | Tests | Failures | Errors | Skipped |
|-------|-------|----------|--------|---------|
| JmsComponentIbmMQTest | 1 | 0 | 1 (env) | 0 |
| JmsReplyToIbmMQTest | 1 | 0 | 1 (env) | 0 |
| All other camel-jms tests | 444 | 0 | 0 | 9 |
| **Total** | **446** | **0** | **2 (env)** | **9** |
The IBM MQ container (`icr.io/ibm-messaging/mq:10.0.1.0-r1`) starts
successfully and the listener is available, but the JMS TCP connection from the
test JVM to the container times out due to Docker bridge network isolation in
the DinD environment. The same issue would affect the previous `10.0.0.0-r4`
image — this is not a version-specific regression.
The upgrade appears safe. The container image pulled and started without
issues.
<details><summary>Error details</summary>
```
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
60.19 s -- JmsComponentIbmMQTest
org.awaitility.core.ConditionTimeoutException: Condition with alias 'IBM MQ
accepting JMS connections'
didn't complete within 1 minutes
Caused by: com.ibm.mq.MQException: JMSCMQ0001: IBM MQ call failed
with compcode '2' ('MQCC_FAILED') reason '2538' ('MQRC_HOST_NOT_AVAILABLE')
Caused by: java.net.ConnectException: Connection refused
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
120.5 s -- JmsReplyToIbmMQTest
(same root cause)
```
</details>
> _Local integration tests run by Hermes 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]
