Skip to content

fix: force LANG=C on MQ 10.0 container to fix JmsReplyToIbmMQTest - #25231

Closed
gnodet wants to merge 1 commit into
apache:dependency/upgrade-ibmmq-10from
gnodet:fix/ibmmq-10-replyto-test
Closed

fix: force LANG=C on MQ 10.0 container to fix JmsReplyToIbmMQTest#25231
gnodet wants to merge 1 commit into
apache:dependency/upgrade-ibmmq-10from
gnodet:fix/ibmmq-10-replyto-test

Conversation

@gnodet

@gnodet gnodet commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

Summary

Fix the JmsReplyToIbmMQTest.testCustomJMSReplyToInOut test failure introduced by the IBM MQ 10.0 upgrade in PR #25107.

  • IBM MQ 10.0 changed the default locale from C to C.utf8, causing the queue manager to use CCSID 1208 (UTF-8) instead of CCSID 819 (ISO 8859-1)
  • This change causes the JMS reply-to mechanism to fail silently — the reply message never reaches DEV.QUEUE.2
  • Force LANG=C on the container to preserve the CCSID 819 behavior from MQ 9.4.x

This is a pragmatic fix to validate the CCSID hypothesis. If CI passes with this change, the CCSID locale change is confirmed as the root cause. A proper fix (supporting CCSID 1208 natively) can be investigated as a follow-up.

Test plan

  • JmsReplyToIbmMQTest.testCustomJMSReplyToInOut should pass (currently fails 3/3 runs)
  • JmsComponentIbmMQTest.testSend should continue to pass
  • No regressions in other JMS tests

Claude Code on behalf of gnodet

MQ 10.0 changed the default locale from C to C.utf8, causing the
queue manager to use CCSID 1208 (UTF-8) instead of 819 (ISO 8859-1).
This change breaks the JMS reply-to test (JmsReplyToIbmMQTest) where
the reply message never reaches DEV.QUEUE.2.

Force the C locale on the container to preserve the CCSID 819 behavior
that was in place with MQ 9.4.x.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

  • First-time contributors require MANUAL approval for the GitHub Actions to run
  • You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
  • You can label PRs using skip-tests and test-dependents to fine-tune the checks executed by this PR.
  • Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

@gnodet

gnodet commented Jul 30, 2026

Copy link
Copy Markdown
Contributor Author

Closing: PR targeting a feature branch doesn't trigger the main build. Will re-create targeting main.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant