You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Clebert Suconic (Jira)" <ji...@apache.org> on 2023/10/26 17:07:00 UTC
[jira] [Updated] (ARTEMIS-4476) Connection Failure Race Conditions in AMQP and Core
[ https://issues.apache.org/jira/browse/ARTEMIS-4476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Clebert Suconic updated ARTEMIS-4476:
-------------------------------------
Summary: Connection Failure Race Conditions in AMQP and Core (was: Connection Failure Race Conditions)
> 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
>
> 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)