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

Posted to issues@activemq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/01/03 18:32:00 UTC

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

    [ https://issues.apache.org/jira/browse/ARTEMIS-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16733343#comment-16733343 ] 

ASF GitHub Bot commented on ARTEMIS-2213:
-----------------------------------------

Github user michaelandrepearce commented on the issue:

    https://github.com/apache/activemq-artemis/pull/2481
  
    Can we close this for the interim?


> 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: yangwei
>            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
(v7.6.3#76005)