[LOG4J2-744] Avoid unnecessary Clock calls when TimestampMessage is logged

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 2.0.1
• Assignee: Remko Popma
• Reporter: Scott Harrington
• Created: 25/Jul/14 03:30
• Updated: 30/Mar/16 14:33
• Resolved: 29/Jul/14 16:24

Description

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.

Issue Links

• is superceded by: LOG4J2-1339 AsyncLogger should not call instanceof TimestampMessage in hot path