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

Reply via email to