You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Justin Bertram (Jira)" <ji...@apache.org> on 2020/01/10 20:22:00 UTC

[jira] [Resolved] (ARTEMIS-2213) Clock drift causing server halt

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

Justin Bertram resolved ARTEMIS-2213.
-------------------------------------
    Resolution: Abandoned

It's been more than a year since the PR for this issue was closed. I assume this is no longer an issue so closing this Jira.

> Clock drift causing server halt
> -------------------------------
>
>                 Key: ARTEMIS-2213
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2213
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 2.6.3
>            Reporter: Wei Yang
>            Priority: Critical
>
> In our production cluster some brokers crashed. There is nothing unusual in the dump stack. After digging into code, we found component was incorrectly expired. When clock drifted back, left time was less than enter time. If the component was not entered in default 120000ms, it would be expired and server was halted.



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