[
https://issues.apache.org/jira/browse/LOG4J2-982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14525661#comment-14525661
]
Gary Gregory commented on LOG4J2-982:
-------------------------------------
When I run {{m33 clean test -pl !log4j-perf}} the v3 patch, I get:
{noformat}
Failed tests:
FlumePersistentAppenderTest.testFailover:209 Received 0 events. Event 1 is
null
FlumePersistentAppenderTest.testLog4Event:137 null
FlumePersistentAppenderTest.testMultiple:154 Received 0 events. Event 1 is
null
FlumePersistentAppenderTest.testSingle:232 null
Tests run: 19, Failures: 4, Errors: 0, Skipped: 0
{noformat}
What do you get?
> 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]
