[
https://issues.apache.org/jira/browse/CAMEL-23677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18113921#comment-18113921
]
Guillaume Nodet commented on CAMEL-23677:
-----------------------------------------
This issue is being investigated by a coding agent (on behalf of gnodet).
Analysis: The @DisabledOnOs(architectures = {"s390x"}) annotation was re-added
after a fix attempt (PR #25266, commit 670620c04a0d) was reverted (commit
4b99a3660d50) because the Artemis container image
icr.io/s390x-oss/activemq-artemis-broker-s390x:2.0.2 cannot be fetched in CI.
The real fix requires either making the container image available or
refactoring the test to use the Artemis test service infrastructure (which
works on s390x) instead of ArtemisContainer directly.
_Note: This comment was generated by an AI coding agent and requires manual
verification._
> Investigate SjmsConnectionRecoveryTest, skipped on s390x
> --------------------------------------------------------
>
> Key: CAMEL-23677
> URL: https://issues.apache.org/jira/browse/CAMEL-23677
> Project: Camel
> Issue Type: Task
> Components: camel-sjms
> Reporter: Federico Mariani
> Assignee: Guillaume Nodet
> Priority: Minor
>
> The test _SjmsConnectionRecoveryTest_ was skipped on *s390x* due to non
> working infrastructure. Such test uses a different approach compared to the
> others, in particular, to test a reconnect scenario it need a *tcp:*
> connection, unlike all the other tests that uses *vm:*.
> Most probably the issue is not in Camel itself, but in the artemis
> configuration. It would be nice to investigate it and try to fix it on s390x
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
