[
https://issues.apache.org/jira/browse/LOG4J2-982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14525685#comment-14525685
]
Gary Gregory edited comment on LOG4J2-982 at 5/3/15 6:15 AM:
-------------------------------------------------------------
Well, it sounds like a bug, see the early comments from the reporter, and my
comments with references to Oracle posts. How often this happens in RL and what
the consequences really are, I have not personally experienced. As usualy YMMV
;-) I'd be happy to get a 2.3 ASAP and leave this for the next iteration. Are
you available to push out an RC?
was (Author: garydgregory):
Well, it sounds like a bug, see the early comments from the reporter, and my
comments with references to Oracle posts. How often this happens in RL and what
the consequences really are, I have not personally experienced. As usualy YMMV
;-) I'd be happy to push 2.3 ASAP and leave this for the next iteration. Are
you available to push out an RC?
> 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-v2.patch, LOG4J2-982-v3.patch,
> 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]
