[jira] [Created] (LOG4J2-744) Aviod unnecessary Clock calls when TimestampMessage is logged

["Scott Harrington (JIRA)" <ji...@apache.org>]

Scott Harrington created LOG4J2-744:
---------------------------------------

             Summary: Aviod unnecessary Clock calls when TimestampMessage is logged
                 Key: LOG4J2-744
                 URL: https://issues.apache.org/jira/browse/LOG4J2-744
             Project: Log4j 2
          Issue Type: Improvement
            Reporter: Scott Harrington
            Priority: Minor


The TimestampMessage interface was introduced in LOG4J2-53 and revised for AsyncLogger in LOG4J2-455.

I've observed that Clock.currentTimeMillis is still called which should not be necessary.

I have two patches, one which adds JUnit tests that demonstrate the unnecessary Clock calls, and one which fixes the issue for both AsyncLogger and "traditional" configurations.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org