[ 
https://issues.apache.org/jira/browse/ARTEMIS-4338?focusedWorklogId=868768&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-868768
 ]

ASF GitHub Bot logged work on ARTEMIS-4338:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 30/Jun/23 18:37
            Start Date: 30/Jun/23 18:37
    Worklog Time Spent: 10m 
      Work Description: jbertram commented on PR #4530:
URL: 
https://github.com/apache/activemq-artemis/pull/4530#issuecomment-1615054668

   I need some help with the implementation of 
`org.apache.activemq.artemis.core.protocol.ProtocolHandler.ProtocolDecoder#exceptionCaught`
 so anybody with Netty know-how please speak up!




Issue Time Tracking
-------------------

    Worklog Id:     (was: 868768)
    Time Spent: 20m  (was: 10m)

> Stomp connection fails with 2.29.0
> ----------------------------------
>
>                 Key: ARTEMIS-4338
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4338
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: STOMP
>    Affects Versions: 2.29.0
>            Reporter: Otavio Rodolfo Piske
>            Assignee: Justin Bertram
>            Priority: Blocker
>         Attachments: camel-stomp-test-debug-2.28.0.log, 
> camel-stomp-test-debug-2.29.0.log
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> 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)

Reply via email to