[
https://issues.apache.org/jira/browse/ARTEMIS-4476?focusedWorklogId=890314&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-890314
]
ASF GitHub Bot logged work on ARTEMIS-4476:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 13/Nov/23 15:48
Start Date: 13/Nov/23 15:48
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on code in PR #4669:
URL: https://github.com/apache/activemq-artemis/pull/4669#discussion_r1391299925
##########
artemis-hawtio/artemis-plugin/src/main/webapp/plugin/js/components/consumers.js:
##########
@@ -106,7 +106,8 @@ var Artemis;
{name: "Messages Acknowledged", visible: false},
{name: "Messages Acknowledged awaiting Commit", visible: false},
{name: "Last Delivered Time", visible: false},
- {name: "Last Acknowledged Time", visible: false}
+ {name: "Last Acknowledged Time", visible: false},
+ {name "status", visible: false}
Review Comment:
thanks a lot.. that's why it was not working.
Issue Time Tracking
-------------------
Worklog Id: (was: 890314)
Time Spent: 4.5h (was: 4h 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: 4.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)
