logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Hsueh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-628) Cannot set log4j.Clock with Async appender
Date Mon, 05 May 2014 19:49:16 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13989899#comment-13989899

Bryan Hsueh commented on LOG4J2-628:

Tested, and works, thanks.  I see this message log 7 times at the start though, "ERROR StatusLogger
Unable to locate ServletContext".  Does this have to do with my build process?  Likewise,
I can no longer find SocketServer.  I pulled your revision from github and followed the build

> 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

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message