logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remko Popma (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (LOG4J2-628) Cannot set log4j.Clock with Async appender
Date Fri, 02 May 2014 23:15:16 GMT

     [ https://issues.apache.org/jira/browse/LOG4J2-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Remko Popma reassigned LOG4J2-628:
----------------------------------

    Assignee: Remko Popma

> 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-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message