logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralph Goers (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (LOG4J2-53) Better control over timestamp
Date Tue, 01 May 2012 06:25:46 GMT

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

Ralph Goers resolved LOG4J2-53.

       Resolution: Fixed
    Fix Version/s: 2.0-alpha1
         Assignee: Ralph Goers

TimestampMessage should address this.
> Better control over timestamp
> -----------------------------
>                 Key: LOG4J2-53
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-53
>             Project: Log4j 2
>          Issue Type: New Feature
>            Reporter: scott deboy
>            Assignee: Ralph Goers
>             Fix For: 2.0-alpha1
> For apps which require very accurate event times, the timestamp must be provided by the
app.  In log4j 1.2 it is assigned when the event is created, which is the time the event is
appended.  This could be many milliseconds after the actual generation of the event.  This
also gives the app the ability to collect event milestones and then choose at the end of the
processing whether or not to have them sent to an appender and still control the timestamp.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


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

View raw message