You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Remko Popma (JIRA)" <ji...@apache.org> on 2015/04/07 14:23:12 UTC
[jira] [Comment Edited] (LOG4J2-982) Use System.nanoTime() to
measure time intervals
[ https://issues.apache.org/jira/browse/LOG4J2-982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14483084#comment-14483084 ]
Remko Popma edited comment on LOG4J2-982 at 4/7/15 12:23 PM:
-------------------------------------------------------------
I created a separate ticket LOG4J2-993 for the deadlock issue.
Gary, I named you as the reporter since you found it first. I hope that is okay.
was (Author: remkop@yahoo.com):
I created a separate ticket LOG4J2-993 for the deadlock issue.
> 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.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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org