Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.0.1
-
Component/s: None
-
Labels:None
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.
Attachments
Issue Links
- is superceded by
-
LOG4J2-1339 AsyncLogger should not call instanceof TimestampMessage in hot path
-
- Closed
-