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.

[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

---

🔬 Scalpel shadow comparison — Scalpel: 14 tested, 29 compile-only — current: 0 all tested

Maveniverse Scalpel detected 43 affected modules (current approach: 0).

⚠️ Modules only in Scalpel (43)

• apache-camel
• camel-activemq
• camel-activemq6
• camel-allcomponents
• camel-amqp
• camel-catalog
• camel-catalog-console
• camel-catalog-lucene
• camel-catalog-maven
• camel-catalog-suggest
• camel-componentdsl
• camel-csimple-maven-plugin
• camel-endpointdsl
• camel-endpointdsl-support
• camel-itest
• camel-jbang-core
• camel-jbang-it
• camel-jbang-main
• camel-jbang-mcp
• camel-jbang-plugin-edit
• camel-jbang-plugin-generate
• camel-jbang-plugin-kubernetes
• camel-jbang-plugin-mcp
• camel-jbang-plugin-route-parser
• camel-jbang-plugin-test
• camel-jbang-plugin-tui
• camel-jbang-plugin-validate
• camel-jms
• camel-kamelet-main
• camel-launcher
• camel-launcher-container
• camel-report-maven-plugin
• camel-route-parser
• camel-test-infra-all
• camel-test-infra-ibmmq
• camel-yaml-dsl
• camel-yaml-dsl-deserializers
• camel-yaml-dsl-maven-plugin
• camel-yaml-dsl-validator
• camel-yaml-dsl-validator-maven-plugin
• coverage
• docs
• dummy-component

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

Skip-tests mode would test 14 modules (1 direct + 13 downstream), skip tests for 29 (generated code, meta-modules)

Modules Scalpel would test (14)

• camel-activemq
• camel-activemq6
• camel-amqp
• camel-jbang-mcp
• camel-jbang-plugin-mcp
• camel-jbang-plugin-route-parser
• camel-jbang-plugin-tui
• camel-jbang-plugin-validate
• camel-jms
• camel-launcher-container
• camel-test-infra-all
• camel-test-infra-ibmmq
• camel-yaml-dsl-validator
• camel-yaml-dsl-validator-maven-plugin

Modules with tests skipped (29)

• apache-camel
• camel-allcomponents
• camel-catalog
• camel-catalog-console
• camel-catalog-lucene
• camel-catalog-maven
• camel-catalog-suggest
• camel-componentdsl
• camel-csimple-maven-plugin
• camel-endpointdsl
• camel-endpointdsl-support
• camel-itest
• camel-jbang-core
• camel-jbang-it
• camel-jbang-main
• camel-jbang-plugin-edit
• camel-jbang-plugin-generate
• camel-jbang-plugin-kubernetes
• camel-jbang-plugin-test
• camel-kamelet-main
• camel-launcher
• camel-report-maven-plugin
• camel-route-parser
• camel-yaml-dsl
• camel-yaml-dsl-deserializers
• camel-yaml-dsl-maven-plugin
• coverage
• docs
• dummy-component

ℹ️ Shadow mode — Scalpel observes but does not affect test execution. Learn more

All tested modules (44 modules)

• Camel :: AMQP
• Camel :: ActiveMQ 5.x
• Camel :: ActiveMQ 6.x
• Camel :: All Components Sync point
• Camel :: Assembly
• Camel :: Catalog :: CSimple Maven Plugin (deprecated)
• Camel :: Catalog :: Camel Catalog
• Camel :: Catalog :: Camel Report Maven Plugin
• Camel :: Catalog :: Camel Route Parser
• Camel :: Catalog :: Console
• Camel :: Catalog :: Dummy Component
• Camel :: Catalog :: Lucene (deprecated)
• Camel :: Catalog :: Maven
• Camel :: Catalog :: Suggest
• Camel :: Component DSL
• Camel :: Coverage
• Camel :: Docs
• Camel :: Endpoint DSL
• Camel :: Endpoint DSL :: Support
• Camel :: Integration Tests
• Camel :: JBang :: Core
• Camel :: JBang :: Integration tests
• Camel :: JBang :: MCP
• Camel :: JBang :: Main
• Camel :: JBang :: Plugin :: Edit
• Camel :: JBang :: Plugin :: Generate
• Camel :: JBang :: Plugin :: Kubernetes
• Camel :: JBang :: Plugin :: MCP
• Camel :: JBang :: Plugin :: Route Parser
• Camel :: JBang :: Plugin :: TUI
• Camel :: JBang :: Plugin :: Testing
• Camel :: JBang :: Plugin :: Validate
• Camel :: JMS
• Camel :: Kamelet Main
• Camel :: Launcher
• Camel :: Launcher :: Container
• Camel :: Parent
• Camel :: Test Infra :: All test services
• Camel :: Test Infra :: IBM MQ
• Camel :: YAML DSL
• Camel :: YAML DSL :: Deserializers
• Camel :: YAML DSL :: Maven Plugins
• Camel :: YAML DSL :: Validator
• Camel :: YAML DSL :: Validator Maven Plugin

---

⚙️ 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.