[
https://issues.apache.org/jira/browse/LOG4J2-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13990641#comment-13990641
]
Gary Gregory commented on LOG4J2-628:
-------------------------------------
Please note that I am working on the whole server side of Log4j to receive JSON
and XML events. This is not in trunk yet. If would kindly request that you
consider delaying commits in this area if possible to make my keeping up with
trunk less painful. Thank you. Gary.
> 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
> Fix For: 2.0-rc2
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
