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] [Updated] (LOG4J2-1130) CsvLogEventLayout NanoTime timestamp is always zero.
Date Thu, 06 Oct 2016 05:28:21 GMT

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

Remko Popma updated LOG4J2-1130:
--------------------------------
    Fix Version/s:     (was: 2.7)
                   2.8

> CsvLogEventLayout NanoTime timestamp is always zero.
> ----------------------------------------------------
>
>                 Key: LOG4J2-1130
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1130
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Layouts
>    Affects Versions: 2.4
>            Reporter: Remko Popma
>             Fix For: 2.8
>
>
> CsvLogEventLayout generates NanoTime timestamps but these are always zero.
> To fix this, add the below code to the CsvLogEventLayout constructor:
> {code}
>       // LOG4J2-1074 Switch to actual clock if nanosecond timestamps are required in
config.
>       // LoggerContext will notify known NanoClockFactory users that the configuration
has changed.
>       NanoClockFactory.setMode(NanoClockFactory.Mode.System);
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
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