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 2021/08/09 17:56:05 UTC

[jira] [Closed] (ARTEMIS-3271) Avoid Multi Thread measurement on Critical Analyzer

     [ https://issues.apache.org/jira/browse/ARTEMIS-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Clebert Suconic closed ARTEMIS-3271.
------------------------------------
    Resolution: Fixed

> Avoid Multi Thread measurement on Critical Analyzer
> ---------------------------------------------------
>
>                 Key: ARTEMIS-3271
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3271
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 2.17.0
>            Reporter: Clebert Suconic
>            Priority: Major
>             Fix For: 2.18.0
>
>          Time Spent: 5h 20m
>  Remaining Estimate: 0h
>
> The Critical Analyzer could be called from multiple Threads.
>  
> As a result, I am afraid there could be a situation that left time was updated at a wrong pace.. leaving to inconsistencies.
>  
>  
> I'm improving it to only consider a single thread from all the calls. Any calls from multi-threading should be ignored... All we need is to capture one thread hanging and detect a dead lock.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)