HyukjinKwon opened a new pull request, #56660: URL: https://github.com/apache/spark/pull/56660
### What changes were proposed in this pull request? Upgrade `log4j` from 2.25.x to **2.26.0** (`pom.xml` and `dev/deps/spark-deps-hadoop-3-hive-2.3`). ### Why are the changes needed? Under JDK 25, log4j2's `ThrowableStackTraceRenderer` throws `NullPointerException: Cannot read field "stackLength" because "metadata" is null` when rendering any logged exception's stack trace. On Spark this surfaces as `FsHistoryProviderSuite` "provider reports error after FS leaves safe mode" failing on the JDK 25 scheduled build. Example failing upstream run (Build / Java25): https://github.com/apache/spark/actions/runs/27894816608 log4j 2.26.0 fixes the renderer (snapshots the stack trace during metadata population; upstream LOG4J2 #3940 / #3955). ### Does this PR introduce any user-facing change? No. Build/logging dependency upgrade. ### How was this patch tested? Validated on a fork. - `FsHistoryProviderSuite` "provider reports error after FS leaves safe mode" is GREEN on **JDK 25** with this bump: https://github.com/HyukjinKwon/spark/actions/runs/27929988232 - Fully GREEN combined Maven (Scala 2.13, JDK 21) run that includes this log4j bump, 0 failed jobs (the same suite also fails on JDK 21 without the bump): **https://github.com/HyukjinKwon/spark/actions/runs/27935083986** - A combined JDK 25 proof run is also in progress: https://github.com/HyukjinKwon/spark/actions/runs/27943439418 ### Was this patch authored or co-authored using generative AI tooling? Yes. Drafted with Claude Code (Anthropic) and reviewed before submission. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
