You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So both log files have entries with invalid date 2024.12.31 when it was 2023.12.31. Especially this line makes me wonder if there is a bug in the slf4j, in logback, in my comfiguration (or in joda time DateTime class):
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have simple backup tool written in scala. Run command is:
java -Xmx6144m -Dlogback.configurationFile=/home/jk/binh/BckpTool.xml -cp /home/jk/bin2/BckpTool/BckpTool-assembly-1.0.jar
Part of the
build.sbt
file with versions is below:parts of the
BckpTool.scala
is below:Content of /
home/jk/binh/BckpTool.xml
Content of
/home/jk/tmp/cpVMSummary.log
And short content of
/home/jk/tmp/cpVM.log
Zoned/LocalDateTime and time zone using Ammonite Repl:
So both log files have entries with invalid date 2024.12.31 when it was 2023.12.31. Especially this line makes me wonder if there is a bug in the slf4j, in logback, in my comfiguration (or in joda time DateTime class):
It seems that for some reason logging cannot handle year correctly on 2023.12.31. so logging on 2023.12.31 produce invalid log entries 2024.12.31.
Any ideas what is the problem here? Bug in
lsf4j
or inlogback
or in my config?Beta Was this translation helpful? Give feedback.
All reactions