gnodet commented on PR #25292: URL: https://github.com/apache/camel/pull/25292#issuecomment-5178387507
## ⚠️ Local IT results for `7d28291` — correction to previous report **Previous comment on this commit reported a timeout issue — that analysis was incorrect.** The actual root cause is a Docker networking limitation in the ForgeBot test environment. ### Diagnosis | Check | Result | |-------|--------| | IBM MQ 10.0.0.0-r3 container starts? | ✅ Yes — Queue Manager QM1 operational, listener RUNNING on port 1414 | | MQ listener active inside container? | ✅ Yes — `DISPLAY LSSTATUS(*)` shows `STATUS(RUNNING)` | | Port reachable from host (`localhost`)? | ❌ No — `Connection refused` | | Port reachable via container IP? | ❌ No — no route to `172.17.0.0/16` | | Other containers (e.g. nginx) reachable? | ❌ No — same issue | | `docker0` bridge present? | ❌ No — not visible from this namespace | ### Root Cause ForgeBot runs inside a Docker container that shares the Docker daemon via **socket mounting** (`/var/run/docker.sock`). This means: - ForgeBot can **create and manage** sibling containers via the Docker API - ForgeBot **cannot connect** to sibling containers' published ports — they exist in a different network namespace with no route from the ForgeBot container This affects **all** Testcontainers-based integration tests, not just IBM MQ. The timeout mentioned in the previous comment was a symptom, not the cause — increasing it from 30s to 120s still fails because the port is unreachable, not slow. ### What we verified - The IBM MQ 10.0.0.0-r3 container **starts successfully** and the queue manager initializes normally - This is a major version upgrade (9.4.5.0 → 10.0.0.0) which may have behavioral changes, but **container startup is not broken** - The 428/436 non-IBM-MQ JMS tests (using embedded ActiveMQ) all pass — only the 2 tests requiring the Docker container fail ### Recommendation This PR should be verified by: 1. **CI** — the automated CI pipeline (which has proper Docker networking) 2. **A maintainer running ITs locally** in a standard Docker environment (not DinD) 3. Specifically test: `mvn verify -pl components/camel-jms -Dtest=JmsComponentIbmMQTest,JmsReplyToIbmMQTest` The container image itself appears healthy — the issue is purely environmental. > _Local integration tests run by ForgeBot on behalf of @gnodet_ > _Tests run without `-Dci.env.name` to include ITs disabled on GitHub Actions CI_ > _Environment limitation: Docker socket mounting prevents network connectivity to sibling containers_ -- 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]
