[prev in list] [next in list] [prev in thread] [next in thread] 

List:       log4j-dev
Subject:    [jira] [Assigned] (LOG4J2-744) Avoid unnecessary Clock calls when TimestampMessage is logged
From:       "Remko Popma (JIRA)" <jira () apache ! org>
Date:       2014-07-29 15:29:39
Message-ID: JIRA.12729648.1406259029470.65718.1406647779642 () arcas
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/LOG4J2-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Remko Popma reassigned LOG4J2-744:
----------------------------------

    Assignee: Remko Popma

> Avoid 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
> Assignee: Remko Popma
> Priority: Minor
> Attachments: ClockBenchmark-jdk1.6.0_31.txt, ClockBenchmark-jdk1.7.0_45.txt, \
> ClockBenchmark.java, LOG4J2-744-test.patch, LOG4J2-744.patch 
> 
> 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


[prev in list] [next in list] [prev in thread] [next in thread]