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

Ralph Goers edited comment on LOG4J2-1883 at 4/13/17 9:54 PM:
--------------------------------------------------------------

No, none of those help. The first two are just formatting methods. As its name 
implies, currentTimeMillis gets the time in milliseconds, not microseconds. 
nanoTime will get the number of nanoseconds since the JVM started, which is 
useless for displaying wall clock time. If you are somehow trying to 
concatenate the nanoseconds to the milliseconds the result doesn't make any 
sense since they don't have a comment point of reference and there is no way to 
create one.


was (Author: ralph.go...@dslextreme.com):
No, none of those help. The first two are just formatting methods. As its name 
implies, currentTimeMillis gets the time in milliseconds, not microseconds. 
nanoTime will get the number of nanoseconds since the JVM started, which is 
useless for displaying wall clock time.

> Timestamp does not seem to support microseconds level
> -----------------------------------------------------
>
>                 Key: LOG4J2-1883
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1883
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Configurators
>         Environment: Linux with any JDK including JDK1.8
>            Reporter: Madhava Dass
>            Priority: Critical
>
> Used log4j and 'log4j2.xml' to configure timestamp format as:
> {code}
> <?xml version="1.0" encoding="UTF-8"?>
> <Configuration status="WARN">
>     <Appenders>
>         <Console name="Console" target="SYSTEM_OUT">
>             <PatternLayout 
> pattern="[%d{yyyy-MM-dd'T'HH:mm:ss.SSSXXX}{UTC}][%level][%logger{36}]:%msg%n"/>
>         </Console>
>     </Appenders>
>     <Loggers>
>         <Root level="DEBUG">
>             <AppenderRef ref="Console"/>
>         </Root>
>     </Loggers>
> </Configuration>
> {code}
> This pattern produces the time stamp as:
> {code}
> [2017-03-29T13:55:28.363000][null]:[Thread-1]: - <message>
> {code}
> The desired output is:
> {code}
> [2017-03-29T13:55:28.363701-07:00][null]:[Thread-1]: - <message>
> {code}
> Different versions of JDKs were tried including JDK 1.8. It does not seem to 
> make any difference in the outcome.
> Is there a way to get the desired time stamp through pattern matching 
> configuration in the '*.xml' file?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to