[
https://issues.apache.org/jira/browse/ARTEMIS-4338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738613#comment-17738613
]
Robbie Gemmell commented on ARTEMIS-4338:
-----------------------------------------
There is a link to CAMEL-19561, which notes the issue was seen with
camel-stomp, so probably just running its integration tests. CAMEL-19561 in
turn links to [https://github.com/apache/camel/pull/10540] to revert to
2.28.0...so probably just undoing that and run the camel-stomp tests.
Stomp failures are visible in
[https://ci-builds.apache.org/job/Camel/job/Camel%20JDK17/job/main/967/#showFailuresLink]
which presumably will show how they are being run, if its anything special.
> Stomp connection fails with 2.29.0
> ----------------------------------
>
> Key: ARTEMIS-4338
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4338
> Project: ActiveMQ Artemis
> Issue Type: Task
> Components: STOMP
> Affects Versions: 2.29.0
> Reporter: Otavio Rodolfo Piske
> Assignee: Justin Bertram
> Priority: Major
> Attachments: camel-stomp-test-debug-2.28.0.log,
> camel-stomp-test-debug-2.29.0.log
>
>
> Recently we tried upgrading to Artemis 2.29, but when doing so our
> integration tests started to fail. No code was changed as part of the upgrade.
> With 2.29, the connection seems to fail due to a connection timeout:
>
> {noformat}
> 2023-06-29 07:51:40,739 [Impl$6@b91d8c4)] WARN server
> - AMQ222067: Connection failure has been detected: AMQ229014: Did not
> receive data from /127.0.0.1:50934 within the 60000ms connection TTL. The
> connection will now be closed. [code=CONNECTION_TIMEDOUT]{noformat}
>
> I wasn't able to determine the problem, so I am attaching the debug logs for
> an execution with 2.28 and another with 2.29.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
