[jira] [Work logged] (ARTEMIS-4476) Connection Failure Race Conditions in AMQP and Core

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

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

                Author: ASF GitHub Bot
            Created on: 26/Oct/23 17:08
            Start Date: 26/Oct/23 17:08
    Worklog Time Spent: 10m 
      Work Description: clebertsuconic opened a new pull request, #4656:
URL: https://github.com/apache/activemq-artemis/pull/4656

   (no comment)




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

            Worklog Id:     (was: 887432)
    Remaining Estimate: 0h
            Time Spent: 10m

> Connection Failure Race Conditions in AMQP and Core
> ---------------------------------------------------
>
>                 Key: ARTEMIS-4476
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4476
>             Project: ActiveMQ Artemis
>          Issue Type: Task
>            Reporter: Clebert Suconic
>            Assignee: Clebert Suconic
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Failure Detection has a possibility to a race condition with the processing of the client packets (or frames in the case of AMQP).
> This is because Netty detects the failure and removes the connection objects while the packets are still processing things. 
> I was not able to reproduce this particular issue, but I have seen a case from a memory dump where the consumer was created while the connection was already dropped, leaving the consumer isolated without any communication with clients.
> That particular case I could see a possibility because of these races.
> I am adding tests to exercise connection failure in stress and I was able to reproduce other issues.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)