[
https://issues.apache.org/jira/browse/ARTEMIS-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729020#comment-16729020
]
ASF GitHub Bot commented on ARTEMIS-2213:
-----------------------------------------
Github user wy96f commented on the issue:
https://github.com/apache/activemq-artemis/pull/2481
@franz1981 thanks for the explanation. We have verified nanoTime is
correctly supported. We observed the queue delivered messages and received no
messages for abount 2mins, then broker is killed. Three brokers had been killed
this week. That was weird. The dumped stacktrace is attached. Could you shed us
some light? :)
[https://gist.github.com/wy96f/1a5c2f481e70d8dabde70f3a07eb57b7](url)
> 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)
