[LOG4J2-455] RingBufferLogEvent should use Messsage timestamp first

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0-beta9
• Component/s: Appenders
• Assignee: Remko Popma
• Reporter: robin zhang tao
• Created: 22/Nov/13 08:21
• Updated: 24/Dec/13 01:41
• Resolved: 23/Dec/13 14:57

Description

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();