[
https://issues.apache.org/jira/browse/LOG4J2-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905468#comment-15905468
]
Remko Popma edited comment on LOG4J2-1844 at 3/10/17 5:46 PM:
--------------------------------------------------------------
I believe the specified pattern is wrong and should be {{%d\{yyyy-MM-dd
HH:mm:ss.SSS\}}} instead: lowercase {{mm}} stands for "minutes", uppercase
{{MM}} is needed if you want to express months.
Please close if this solves the problem, or re-open if I misunderstood.
was (Author: rem...@yahoo.com):
I believe the specified pattern is wrong and should be {{ %d\{yyyy-MM-dd
HH:mm:ss.SSS\}}} instead: lowercase {{mm}} stands for "minutes", uppercase
{{MM}} is needed if you want to express months.
Please close if this solves the problem, or re-open if I misunderstood.
> Not the correct value of the month in the log
> ---------------------------------------------
>
> Key: LOG4J2-1844
> URL: https://issues.apache.org/jira/browse/LOG4J2-1844
> Project: Log4j 2
> Issue Type: Bug
> Components: API
> Affects Versions: 2.8.1
> Environment: windows RUS (v.7 and 8.1 is accurate)
> eclipse 4.5.2
> java jdk 1.8.0_74
> Reporter: Vasiliy Ponomarenko
> Assignee: Remko Popma
> Labels: month
>
> if pattern contains Month like {{%d\{yyyy-mm-dd HH:mm:ss.SSS\}}}
> log has wrong Month value
> Window 8.1 like Month value = 19 or 34 or 35 or 36
> 2017-19-10 16:19:05.535 \[main\] for date 2017-03-10
> Window 7 like Month value = current value - 1
> 2017-02-10 16:19:05.535 \[main\] for date 2017-03-10
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
