You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@logging.apache.org by wd...@poczta.fm on 2017/07/18 16:20:35 UTC

How to unsubscribe?

Please help me to unsubscribe the mailing list!Sending to dev-unsubscribe simply doesn't work.WOd: "chandra (JIRA)" <jira@apache.org>Do: dev@logging.apache.org; Wysłane: 17:50 Wtorek 2017-07-18Temat: [jira] [Commented] (LOG4J2-1883) Timestamp does not seem to support microseconds level> 
>     [ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091742#comment-16091742 ] 
> 
> chandra commented on LOG4J2-1883:
> ---------------------------------
> 
> Although, it's nice to maintain a nanosecond level accuracy for time keeping. I am still struggling if it even makes sense in recording a logevent at a sub-millisecond level accuracy in working applications.  Also, the reliability of nano-level precision is tightly dependent on the capability of the hardware -- no matter which method you use. 
> 
> I've already pointed it out earlier: https://issues.apache.org/jira/browse/LOG4J2-1883?focusedCommentId=15976019
> 
> [~jvz] [~Anthony Maire]  thoughts? 
> 
> > 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}
> > 
> > 
> >     
> >         
> >             
> >         
> >     
> >     
> >         
> >             
> >         
> >     
> > 
> > {code}
> > This pattern produces the time stamp as:
> > {code}
> > [2017-03-29T13:55:28.363000][null]:[Thread-1]: - 
> > {code}
> > The desired output is:
> > {code}
> > [2017-03-29T13:55:28.363701-07:00][null]:[Thread-1]: - 
> > {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.4.14#64029)
>