[
https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16092220#comment-16092220
]
Gary Gregory edited comment on LOG4J2-1883 at 7/18/17 9:33 PM:
---------------------------------------------------------------
I really hope we can move to Java 8 BEFORE July 2019, which feels like 200
years from now. I do not see the point of handcuffing ourselves like that. I
get plenty of 'we can't touch that' at work as it is. We could move to Java 8
TODAY as far as I am concerned (well, for 2.10, since we are ready for 2.9 it I
think).
(If we really are going to drag a Java 7 bowling ball around for two more
years, then yeah, creating our own Instant class makes sense. Yikes.)
was (Author: garydgregory):
I really hope we can move to Java 8 BEFORE July 2019, which feels like 200
years from now. I do not see the point of handcuffing ourselves like that. I
get plenty of 'we can't touch that' at work as it is. We could move to Java 8
TODAY as far as I am concerned (well, for 2.10, since we are ready for 2.9 it I
think).
> 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.4.14#64029)
