[
https://issues.apache.org/jira/browse/LOG4J2-982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14375141#comment-14375141
]
Gary Gregory commented on LOG4J2-982:
-------------------------------------
Here is something related http://bugs.java.com/view_bug.do?bug_id=6876279
Notice this:
{quote}
However due to historical (and continual) bugs in those OS time services the VM
has evolved to add extra code - in particular for nanoTime ensuring that it is
a monotonic non-decreasing time source as required.
{quote}
And this https://blogs.oracle.com/dholmes/entry/inside_the_hotspot_vm_clocks
> Use System.nanoTime() to measure time intervals
> -----------------------------------------------
>
> Key: LOG4J2-982
> URL: https://issues.apache.org/jira/browse/LOG4J2-982
> Project: Log4j 2
> Issue Type: Improvement
> Components: Core, Flume Appender
> Reporter: Mikhail Mazurskiy
> Priority: Minor
> Attachments: LOG4J2-982.patch
>
>
> Unlike {{System.currentTimeMillis()}}, which can jump/slew forward and
> backwards, {{System.nanoTime()}} is a monotonic clock (at least it should be)
> and hence it should be used to measure time intervals (timeouts/delays/etc).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
