[
https://issues.apache.org/jira/browse/ARTEMIS-4476?focusedWorklogId=889727&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-889727
]
ASF GitHub Bot logged work on ARTEMIS-4476:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 09/Nov/23 12:50
Start Date: 09/Nov/23 12:50
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on code in PR #4656:
URL: https://github.com/apache/activemq-artemis/pull/4656#discussion_r1387956298
##########
artemis-server/src/main/java/org/apache/activemq/artemis/core/management/impl/QueueControlImpl.java:
##########
@@ -2048,6 +2048,37 @@ public void deliverScheduledMessages(String filter)
throws Exception {
}
}
+ @Override
+ public String verifyConnections() throws Exception {
Review Comment:
hmmm... I need a better name for this method...
getInvalidConnections()
inspectInvalidConnections
any other ideas?
Issue Time Tracking
-------------------
Worklog Id: (was: 889727)
Time Spent: 1.5h (was: 1h 20m)
> 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: 1.5h
> 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)
