[
https://issues.apache.org/jira/browse/CAMEL-23677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Federico Mariani updated CAMEL-23677:
-------------------------------------
Description:
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
was:
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
> 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
> 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)
