[
https://issues.apache.org/jira/browse/ARTEMIS-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728643#comment-16728643
]
ASF GitHub Bot commented on ARTEMIS-2213:
-----------------------------------------
Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/2481
I dont see how this handles clock drift if im honest. The test case doesnt
actually cause a drift in nano.
Also Nanoseconds also are from an arbitary offset on the cpu, and afaik not
from wall clock. So isnt subject to drift like millis are
> 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)
