Skip to content

chore(camel-test-infra-ibmmq): upgrade ibm.mq.container to 10.0.0.0-r1#24017

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
automated/upgrade-ibm-mq-container-10.0.0.0-r1
Open

chore(camel-test-infra-ibmmq): upgrade ibm.mq.container to 10.0.0.0-r1#24017
github-actions[bot] wants to merge 1 commit into
mainfrom
automated/upgrade-ibm-mq-container-10.0.0.0-r1

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

This PR updates the ibm.mq.container container image to version 10.0.0.0-r1.

Update Details

  • Property: ibm.mq.container
  • Image: icr.io/ibm-messaging/mq
  • File: /home/runner/work/camel/camel/test-infra/camel-test-infra-ibmmq/src/main/resources/org/apache/camel/test/infra/ibmmq/services/container.properties
  • Old version: 9.4.5.0-r2
  • New version: 10.0.0.0-r1

Verification

Please verify:

  • Container image version is compatible with existing tests
  • No breaking changes in the updated version
  • Tests pass with the new version

Run the following to rebuild the test infra:

mvn clean verify -pl camel-test-infra-ibmmq

Then test the impacted components.


This PR was automatically created by the Container Version Upgrade workflow.

Update ibm.mq.container from 9.4.5.0-r2 to 10.0.0.0-r1
@github-actions github-actions Bot added dependencies Pull requests that update a dependency file container-images For check container upgrades automated For Check Container upgrade labels Jun 15, 2026

@apupier apupier left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

still test errors:

[�[1;31mERROR�[m] �[1;31mTests �[0;1mrun: �[0;1m2�[m, Failures: 0, �[1;31mErrors: �[0;1;31m1�[m, Skipped: 0, Time elapsed: 20.05 s�[1;31m <<< FAILURE!�[m -- in org.apache.camel.component.jms.integration.�[1mDynamicRouteIT�[m
[�[1;31mERROR�[m] org.apache.camel.component.jms.integration.DynamicRouteIT.testDynamicRouteWithJms -- Time elapsed: 20.02 s <<< ERROR!
org.apache.camel.CamelExecutionException: Exception occurred during execution on the exchange: Exchange[61365226208A135-0000000000000002]
	at org.apache.camel.CamelExecutionException.wrapCamelExecutionException(CamelExecutionException.java:60)
	at org.apache.camel.support.ExchangeHelper.extractResultBody(ExchangeHelper.java:704)
	at org.apache.camel.impl.engine.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:594)
	at org.apache.camel.impl.engine.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:590)
	at org.apache.camel.impl.engine.DefaultProducerTemplate.requestBody(DefaultProducerTemplate.java:415)
	at org.apache.camel.component.jms.integration.DynamicRouteIT.testDynamicRouteWithJms(DynamicRouteIT.java:44)
Caused by: org.apache.camel.ExchangeTimedOutException: The OUT message was not received within: 20000 millis due reply message with correlationID: Camel-61365226208A135-0000000000000000 not received on destination: ActiveMQQueue[bar]. Exchange[61365226208A135-0000000000000002]
	at org.apache.camel.component.jms.reply.ReplyManagerSupport.handleTimeout(ReplyManagerSupport.java:194)
	at org.apache.camel.component.jms.reply.ReplyManagerSupport.processReply(ReplyManagerSupport.java:175)
	at org.apache.camel.component.jms.reply.TemporaryQueueReplyHandler.onTimeout(TemporaryQueueReplyHandler.java:62)
	at org.apache.camel.component.jms.reply.CorrelationTimeoutMap.lambda$new$0(CorrelationTimeoutMap.java:41)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
	at java.base/java.lang.Thread.run(Thread.java:1583)

[�[1;31mERROR�[m] �[1;31mTests �[0;1mrun: �[0;1m1�[m, �[1;31mFailures: �[0;1;31m1�[m, Errors: 0, Skipped: 0, Time elapsed: 23.08 s�[1;31m <<< FAILURE!�[m -- in org.apache.camel.component.jms.integration.spring.�[1mJmsSpringLoadBalanceFailOverJMSIT�[m
[�[1;31mERROR�[m] org.apache.camel.component.jms.integration.spring.JmsSpringLoadBalanceFailOverJMSIT.testFailover -- Time elapsed: 23.08 s <<< FAILURE!
java.lang.AssertionError: mock://bar Body of message: 0. Expected: <Hello World> but was: <response is foo>
	at org.apache.camel.component.mock.MockEndpoint.fail(MockEndpoint.java:2075)
	at org.apache.camel.component.mock.MockEndpoint.assertEquals(MockEndpoint.java:2018)
	at org.apache.camel.component.mock.MockEndpoint$7.assertOnIndex(MockEndpoint.java:957)
	at org.apache.camel.component.mock.MockEndpoint.doFailFast(MockEndpoint.java:1806)
	at org.apache.camel.component.mock.MockEndpoint.onExchange(MockEndpoint.java:1784)
	at org.apache.camel.component.mock.MockEndpoint$1.process(MockEndpoint.java:354)
	at org.apache.camel.processor.SendProcessor.sendUsingProducer(SendProcessor.java:267)
	at org.apache.camel.processor.SendProcessor.process(SendProcessor.java:172)
	at org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$SimpleTask.handleFirst(RedeliveryErrorHandler.java:445)
	at org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$SimpleTask.run(RedeliveryErrorHandler.java:421)
	at org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.doRun(DefaultReactiveExecutor.java:202)
	at org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.executeReactiveWork(DefaultReactiveExecutor.java:192)
	at org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.tryExecuteReactiveWork(DefaultReactiveExecutor.java:169)
	at org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:143)
	at org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleMain(DefaultReactiveExecutor.java:59)
	at org.apache.camel.processor.Pipeline.process(Pipeline.java:165)
	at org.apache.camel.impl.engine.CamelInternalProcessor.processNonTransacted(CamelInternalProcessor.java:385)
	at org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:361)
	at org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.process(DefaultAsyncProcessorAwaitManager.java:81)
	at org.apache.camel.support.AsyncProcessorSupport.process(AsyncProcessorSupport.java:32)
	at org.apache.camel.component.jms.EndpointMessageListener.onMessage(EndpointMessageListener.java:136)
	at org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:798)
	at org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:755)
	at org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:733)
	at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:331)
	at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:268)
	at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1478)
	at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1468)
	at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:1328)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
	at java.base/java.lang.Thread.run(Thread.java:1583)

@oscerd oscerd left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same story as its client-side companion #24040: this ibm.mq.container bump to 10.0.0.0-r1 regresses DynamicRouteIT (ExchangeTimedOut) and JmsSpringLoadBalanceFailOverJMSIT against the 10.x server image, per @apupier's local run. Since there are no checks reported on the branch, that manual run is the only signal — and it's red.

The diff is version-consistent (container.properties + the two regenerated metadata.json), and the arch-exclude line is correctly left untouched. I'd suggest holding this together with #24040 until the IBM MQ 10.x reply-to/correlation failures are understood.


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.

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

Labels

automated For Check Container upgrade container-images For check container upgrades dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants