ASAIKS, there are currently only two places that use System.currentTimeMillis() for creating the log event timestamp: * one of the Log4jLogEvent constructors * PatternProcessor#formatFileName - the log event created here is a temporary object used only by the StrSubstitutor
Not 100% sure about the PatternProcessor#formatFileName... Use configurable time or system time here? On Fri, May 2, 2014 at 8:11 AM, Remko Popma <[email protected]> wrote: > In recent Jira ticket LOG4J2-628 "Cannot set log4j.Clock with Async > appender", the user requests that all log event timestamps are generated > from the a configurable Clock. Currently only log event timestamps > generated by Async Loggers are configurable. > > I think it makes sense to do this. > I propose to limit the scope of Clock to log event timestamps only. > I don't propose to use the Clock internally for things like thread > timeouts. > > Thoughts? > > Remko >
