Log4j have release 2.24.2 solving https://github.com/apache/logging-log4j2/issues/3143 -
which can cause LogManager.getLogger() to return null under certain conditions.
The release notes for 2.24.1 (currently in use in spring-boot 3.4.0) was retrofitted with a warning encouraging the upgrade.
Log4j 2.x release notes: https://logging.apache.org/log4j/2.x/release-notes.html#release-notes-2-24-2
Comment From: wilkinsona
Thanks but we don't need an issue for a dependency upgrade such as this. As explained in the issue template that was displayed when you opened this issue, we have some semi-automated tooling that will handle it.
Comment From: YanivKunda
Sorry, it was my mistake not reading the template all the way through... Thanks for the fail-fast response!