[
https://issues.apache.org/jira/browse/ARTEMIS-4338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738617#comment-17738617
]
Otavio Rodolfo Piske commented on ARTEMIS-4338:
-----------------------------------------------
[~jbertram] I am leaving on PTO soon, so I can't prepare an specific
reproducer. However, you can reproduce this problem by running our test that
raised this issue. Here's the steps:
{code:java}
# Clone and build Camel
git clone https://github.com/apache/camel.git
cd camel
# This is the commit immediatelly before I rolled back the upgrade:
git checkout 66c8499c41d5d298c105d56d30bcce2b933fcf10
# Build Camel
./mvnw -Dquickly install
# Go to the camel-stop component dir
cd components/camel-stomp
# Run the test (this will run the test with Artemis 2.29.0) :
mvn -Dtest=StompConsumerTest test
# You can access the logs in the target dir. Just open a new terminal, in the
same dir and run:
tail -5000f target/camel-stomp-test.log
# If you want to run the test with a different version of Artemis, you can do
so with the following command:
mvn -Dtest=StompConsumerTest -Dactivemq-artemis-version=2.28.0 test
{code}
> 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)
