[
https://issues.apache.org/jira/browse/CAMEL-23677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18113983#comment-18113983
]
Claus Ibsen commented on CAMEL-23677:
-------------------------------------
Fixed via https://github.com/apache/camel/pull/26275 (merged as e9db23be8f12 on
main, 4.23.0).
The test now uses an embedded Artemis broker
(ArtemisServiceFactory.createTCPAllProtocolsService()) with a real TCP acceptor
instead of ArtemisContainer, so no platform-specific Docker image is fetched
and the @DisabledOnOs(architectures = {"s390x"}) guard could be removed. This
aligns it with the other camel-sjms tests, which already use ArtemisService.
> 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
> Fix For: 4.23.0
>
>
> 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)
