Affects Version/s: None
Fix Version/s: 2.0.1
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.
|Summary||Aviod unnecessary Clock calls when TimestampMessage is logged||Avoid unnecessary Clock calls when TimestampMessage is logged|
|Status||Open [ 1 ]||In Progress [ 3 ]|
|Status||In Progress [ 3 ]||Resolved [ 5 ]|
|Fix Version/s||2.0.1 [ 12327381 ]|
|Resolution||Fixed [ 1 ]|
|Status||Resolved [ 5 ]||Closed [ 6 ]|