-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NPE in PatternProcessor
when using a UNIX_MILLIS
date pattern
#2346
Labels
appenders:Rolling
Affects log file rolling functionality
bug
Incorrect, unexpected, or unintended behavior of existing code
Milestone
Comments
When replacing the date lookup with '%d{yyyyMMddhhmmssSSS}', there is no issue. |
Can you provide the version of |
@ppkarwasz I apologize, I'm using 2.20.0 |
ppkarwasz
changed the title
NullPointerException when programmatically creating a logger/appender after file configuration has been loaded
NPE in Mar 5, 2024
PatternProcessor
when using a date pattern without a SimpleDateFormat
equivalent
ppkarwasz
changed the title
NPE in
NPE in Mar 5, 2024
PatternProcessor
when using a date pattern without a SimpleDateFormat
equivalentPatternProcessor
when using a UNIX_MILLIS
date pattern
ppkarwasz
added
the
bug
Incorrect, unexpected, or unintended behavior of existing code
label
Mar 5, 2024
LuciferYang
pushed a commit
to apache/spark
that referenced
this issue
Oct 3, 2024
### What changes were proposed in this pull request? The pr aims to upgrade log4j2 from `2.22.1` to `2.24.1`. ### Why are the changes needed? - The full release notes: https:/apache/logging-log4j2/releases/tag/rel%2F2.24.1 https:/apache/logging-log4j2/releases/tag/rel%2F2.24.0 https:/apache/logging-log4j2/releases/tag/rel%2F2.23.1 https:/apache/logging-log4j2/releases/tag/rel%2F2.23.0 - The new version contains some bug fixes: Fix regression in JdkMapAdapterStringMap performance. (apache/logging-log4j2#2238) Fix NPE in PatternProcessor for a UNIX_MILLIS pattern (apache/logging-log4j2#2346) Fix that parameterized message formatting throws an exception when there are insufficient number of parameters. It previously simply didn't replace the '{}' sequence. The behavior changed in 2.21.0 and should be restored for backward compatibility. (apache/logging-log4j2#2380) Fix putAll() in the default thread context map implementation (apache/logging-log4j2#2942) ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Pass GA. ### Was this patch authored or co-authored using generative AI tooling? No. Closes #48029 from panbingkun/SPARK-49541. Authored-by: panbingkun <[email protected]> Signed-off-by: yangjie01 <[email protected]>
attilapiros
pushed a commit
to attilapiros/spark
that referenced
this issue
Oct 4, 2024
### What changes were proposed in this pull request? The pr aims to upgrade log4j2 from `2.22.1` to `2.24.1`. ### Why are the changes needed? - The full release notes: https:/apache/logging-log4j2/releases/tag/rel%2F2.24.1 https:/apache/logging-log4j2/releases/tag/rel%2F2.24.0 https:/apache/logging-log4j2/releases/tag/rel%2F2.23.1 https:/apache/logging-log4j2/releases/tag/rel%2F2.23.0 - The new version contains some bug fixes: Fix regression in JdkMapAdapterStringMap performance. (apache/logging-log4j2#2238) Fix NPE in PatternProcessor for a UNIX_MILLIS pattern (apache/logging-log4j2#2346) Fix that parameterized message formatting throws an exception when there are insufficient number of parameters. It previously simply didn't replace the '{}' sequence. The behavior changed in 2.21.0 and should be restored for backward compatibility. (apache/logging-log4j2#2380) Fix putAll() in the default thread context map implementation (apache/logging-log4j2#2942) ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Pass GA. ### Was this patch authored or co-authored using generative AI tooling? No. Closes apache#48029 from panbingkun/SPARK-49541. Authored-by: panbingkun <[email protected]> Signed-off-by: yangjie01 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
appenders:Rolling
Affects log file rolling functionality
bug
Incorrect, unexpected, or unintended behavior of existing code
Description
NullPointerException when programmatically creating a logger/appender after file configuration has been loaded.
When configuring a logger at runtime like so, i get a Null Pointer Exception.
Configuration
Version:
2.22.02.20.0Operating system: RHEL 8.1
JDK: JDK 17
Logs
The text was updated successfully, but these errors were encountered: