chore(deps): Bump com.ibm.mq:com.ibm.mq.jakarta.client from 9.4.5.1 to 10.0.0.0

[dependabot]

Bumps com.ibm.mq:com.ibm.mq.jakarta.client from 9.4.5.1 to 10.0.0.0.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

🌟 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.

[github-actions]

🧪 CI tested the following changed modules:

• parent

✅ POM dependency changes: targeted tests included

Changed properties: com-ibm-mq-jakarta-client-version

Modules affected by dependency changes (1)

• :camel-test-infra-ibmmq

All tested modules (2 modules)

• Camel :: Parent
• Camel :: Test Infra :: IBM MQ

---

⚙️ View full build and test results

[apupier]

[�[1;31mERROR�[m] �[1;31mTests �[0;1mrun: �[0;1m1�[m, �[1;31mFailures: �[0;1;31m1�[m, Errors: 0, Skipped: 0, Time elapsed: 9.545 s�[1;31m <<< FAILURE!�[m -- in org.apache.camel.component.jms.issues.�[1mJmsReplyToIbmMQTest�[m
[�[1;31mERROR�[m] org.apache.camel.component.jms.issues.JmsReplyToIbmMQTest.testCustomJMSReplyToInOut -- Time elapsed: 5.076 s <<< FAILURE!
org.opentest4j.AssertionFailedError: expected: <My name is Camel> but was: <null>
	at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:1199)
	at org.apache.camel.component.jms.issues.JmsReplyToIbmMQTest.testCustomJMSReplyToInOut(JmsReplyToIbmMQTest.java:44)

[�[1;34mINFO�[m] Running org.apache.camel.component.jms.issues.�[1mJmsReplyToIbmMQTest�[m
[�[1;31mERROR�[m] �[1;31mTests �[0;1mrun: �[0;1m1�[m, �[1;31mFailures: �[0;1;31m1�[m, Errors: 0, Skipped: 0, Time elapsed: 9.131 s�[1;31m <<< FAILURE!�[m -- in org.apache.camel.component.jms.issues.�[1mJmsReplyToIbmMQTest�[m
[�[1;31mERROR�[m] org.apache.camel.component.jms.issues.JmsReplyToIbmMQTest.testCustomJMSReplyToInOut -- Time elapsed: 5.060 s <<< FAILURE!
org.opentest4j.AssertionFailedError: expected: <My name is Camel> but was: <null>
	at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:1199)
	at org.apache.camel.component.jms.issues.JmsReplyToIbmMQTest.testCustomJMSReplyToInOut(JmsReplyToIbmMQTest.java:44)

[oscerd]

Heads-up that this major bump (9.4.5.1 → 10.0.0.0) regresses the IBM MQ integration test JmsReplyToIbmMQTest.testCustomJMSReplyToInOut (expected <My name is Camel> but was <null>), as @apupier already noted. The green GitHub matrix is misleading here — the MQ ITs aren't part of the standard build matrix, so they have to be run manually.

This is tightly coupled with #24017 (the matching ibm.mq.container 10.x server bump) — the client + server jump regress the JMS reply-to/correlation tests together, so the two should be held and investigated as a pair (real product behavior change vs. test config) before either is merged.

The diff itself is a clean, self-consistent one-line property change.

---

Reviewed with Claude Code on behalf of Andrea Cosentino. This review was generated by an AI agent and may contain inaccuracies; please verify all suggestions before applying.

[apupier]

still same issue when using the 10.0.0.0-r1 container:

[�[1;31mERROR�[m] �[1;31mTests �[0;1mrun: �[0;1m1�[m, �[1;31mFailures: �[0;1;31m1�[m, Errors: 0, Skipped: 0, Time elapsed: 9.160 s�[1;31m <<< FAILURE!�[m -- in org.apache.camel.component.jms.issues.�[1mJmsReplyToIbmMQTest�[m
[�[1;31mERROR�[m] org.apache.camel.component.jms.issues.JmsReplyToIbmMQTest.testCustomJMSReplyToInOut -- Time elapsed: 5.062 s <<< FAILURE!
org.opentest4j.AssertionFailedError: expected: <My name is Camel> but was: <null>
	at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:1199)
	at org.apache.camel.component.jms.issues.JmsReplyToIbmMQTest.testCustomJMSReplyToInOut(JmsReplyToIbmMQTest.java:44)

[�[1;34mINFO�[m] Running org.apache.camel.component.jms.issues.�[1mJmsReplyToIbmMQTest�[m
[�[1;31mERROR�[m] �[1;31mTests �[0;1mrun: �[0;1m1�[m, �[1;31mFailures: �[0;1;31m1�[m, Errors: 0, Skipped: 0, Time elapsed: 8.938 s�[1;31m <<< FAILURE!�[m -- in org.apache.camel.component.jms.issues.�[1mJmsReplyToIbmMQTest�[m
[�[1;31mERROR�[m] org.apache.camel.component.jms.issues.JmsReplyToIbmMQTest.testCustomJMSReplyToInOut -- Time elapsed: 5.057 s <<< FAILURE!
org.opentest4j.AssertionFailedError: expected: <My name is Camel> but was: <null>
	at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:1199)
	at org.apache.camel.component.jms.issues.JmsReplyToIbmMQTest.testCustomJMSReplyToInOut(JmsReplyToIbmMQTest.java:44)

[apupier]

release notes of changes is available here: https://www.ibm.com/docs/en/ibm-mq/10.0.x?topic=mq-whats-new-changed-in-1000

[apupier]

potential thing to look at , in the mqjms.log.0, there is this warning:

June 24, 2026, 2:16:34 PM CEST[ForkJoinPool-1-worker-2] com.ibm.mq.jmqi.remote.impl.RemoteTCPConnection
The TCP.ClntSndBuffSize property is not set in mqclient.ini or the JVM system properties. The JVM selected TCP send buffer size of 8,192 bytes is below the required minimum of 32,768. The JVM will therefore request the network layer to use a TCP send buffer size of 32,768 bytes.

EXPLANATION:
The TCP send buffer size selected by the JVM is below the minimum required. The IBM MQ messaging client will hint the network layer to use the specified send buffer size

ACTION:
None.