[
https://issues.apache.org/jira/browse/ARTEMIS-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728969#comment-16728969
]
ASF GitHub Bot commented on ARTEMIS-2213:
-----------------------------------------
Github user franz1981 commented on the issue:
https://github.com/apache/activemq-artemis/pull/2481
Ah, another consideration: nanoTime can actually go backward due to
"starting in an unspecified point of time", but usually this need to be handled
by not comparing directly values and just perform the difference, making use of
numerical overflow to have correct values back, as reported by
https://docs.oracle.com/javase/8/docs/api/java/lang/System.html#nanoTime--.
> 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)
