[
https://issues.apache.org/jira/browse/LOG4J2-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13988580#comment-13988580
]
Remko Popma commented on LOG4J2-628:
------------------------------------
I agree. Also, using the Clock interface for rollover would introduce some
interesting scenarios like the clock going back in time etc that the rollover
logic was not designed for. It may work, but I would prefer to keep the scope
of this change limited to just the log event timestamps for now.
> Cannot set log4j.Clock with Async appender
> ------------------------------------------
>
> Key: LOG4J2-628
> URL: https://issues.apache.org/jira/browse/LOG4J2-628
> Project: Log4j 2
> Issue Type: Question
> Components: Appenders
> Affects Versions: 2.0-rc1
> Environment: Ubuntu 12.04 / Java 7
> Reporter: Bryan Hsueh
> Assignee: Remko Popma
>
> I override log4j.Clock to support a "live" time vs a "simulated" time.
> System.setProperty("log4j.Clock", "teambh.trade.utils.MyClock");
> If I use asynchronous loggers, it works fine and calls my
> Clock:currentTimeMillis().
> If I switch to async appenders, currentTimeMillis() is not called.
> Is this expected behavior or a bug?
> Thanks
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
