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

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

                Author: ASF GitHub Bot
            Created on: 17/May/21 18:06
            Start Date: 17/May/21 18:06
    Worklog Time Spent: 10m 
      Work Description: clebertsuconic edited a comment on pull request #3558:
URL: https://github.com/apache/activemq-artemis/pull/3558#issuecomment-841722974


   @franz1981 ChannelImpl is an area of changes you made... they were meant for 
replication but it seems it's affecting it here.
   
   I suggest we open another thread somewhere. I don't really follow up on 
closed PRs.. specially on this case the discussion won't be about the Critical 
Analyzer.   The critical analyzer seems to be actually capturing it.. which if 
true it was great!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


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

    Worklog Id:     (was: 597876)
    Time Spent: 5h 10m  (was: 5h)

> 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 10m
>  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)

Reply via email to