[
https://issues.apache.org/jira/browse/LOG4J2-944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291309#comment-14291309
]
Ralph Goers commented on LOG4J2-944:
------------------------------------
The spec says "The originator SHOULD include TIME-SECFRAC if its clock accuracy
and performance permit."
This means the milliseconds are not required and can be omitted, but should be
present whenever possible. However, they should not be omitted simply because
the event has a value of zero for them. It should be consistent and either
always contain milliseconds or leave them off.
I would be OK with fixing this.
> Log4j Flume appender is not adding millisecond to the event headers when the
> event is logged at 000 milliseconds.
> -----------------------------------------------------------------------------------------------------------------
>
> Key: LOG4J2-944
> URL: https://issues.apache.org/jira/browse/LOG4J2-944
> Project: Log4j 2
> Issue Type: Bug
> Components: Flume Appender
> Affects Versions: 2.0-rc1
> Reporter: Vinayaka Ramachandra
>
> If the event happens at exact 000 milliseconds, then milliseconds is not
> inserted.
> We are sending the data to Flume appenders in syslog Format. where it will
> add headers. In header the standard time stamp is in Below Format
> 2015-01-06T07:32:43.345-08:00
> But when the event is logged exactly at 000 milliseconds then millisecond
> part is missing as we can see in below code.
> 2015-01-06T07:32:43-08:00
> This cause exception when we process the data including milliseconds.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
