logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "robin zhang tao (JIRA)" <j...@apache.org>
Subject [jira] [Created] (LOG4J2-455) RingBufferLogEvent should use Messsage timestamp first
Date Fri, 22 Nov 2013 08:22:35 GMT
robin zhang tao created LOG4J2-455:

             Summary: RingBufferLogEvent should use Messsage timestamp first
                 Key: LOG4J2-455
                 URL: https://issues.apache.org/jira/browse/LOG4J2-455
             Project: Log4j 2
          Issue Type: Bug
          Components: Appenders
    Affects Versions: 2.0-beta9
            Reporter: robin zhang tao

When AsyncLogger received log message (method  public void log(final Marker marker, final
String fqcn, final Level level, final Message data,
            final Throwable t)), currently it uses  clock.currentTimeMillis() (see at Line
221) as the timestamp.

But it should check the message implements TimestampMessage or not, if yes, should use TimestampMessage.getTimestamp()
as the timestamp, if not , then using clock.currentTimeMillis(). 

The new Code:

data instanceof TimestampMessage ? ((TimestampMessage) data ).getTimestamp() : clock.currentTimeMillis();

This message was sent by Atlassian 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