gnodet commented on PR #21892: URL: https://github.com/apache/camel/pull/21892#issuecomment-4033137263
I've verified the IBM MQ 9.4.5.0-r1 upgrade locally with Docker — both `JmsComponentIbmMQTest` and `JmsReplyToIbmMQTest` pass. **Issue**: IBM MQ 9.4.x enforces authentication by default (MQRC_NOT_AUTHORIZED 2035), unlike 9.3.x which allowed unauthenticated developer connections. **Fix**: The additional commit (`b0c0e54`) adds: - `MQ_APP_PASSWORD` env var to the container (so the `app` user has a known password) - `DEFAULT_APP_USER` / `DEFAULT_APP_PASSWORD` constants in `IbmMQProperties` - MQCSP auth credentials in `ConnectionFactoryHelper` **About the CI failures**: The build step passes, but the test step fails due to unrelated Artemis-based JMS tests (`JmsTransactedDeadLetterChannelNotHandlerRollbackOnExceptionIT`, `JmsToJmsTransactedSecurityIT`, `RouteIdTransactedIT`). These are pre-existing flaky/failing tests in `camel-jms` that use embedded ActiveMQ Artemis (not IBM MQ at all). They get triggered because the CI incremental build runs all of `camel-jms` since it depends on `camel-test-infra-ibmmq`. The actual IBM MQ tests (`JmsComponentIbmMQTest`, `JmsReplyToIbmMQTest`) are skipped on CI by design (`@DisabledIfSystemProperty(named = "ci.env.name")`) and pass locally with Docker. -- 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]
