Skip to content
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

Upgrade log4j to 2.24.2 to resolve broken logger initialization in 2.24.1 #43318

Closed
YanivKunda opened this issue Nov 28, 2024 · 2 comments
Closed

Comments

@YanivKunda
Copy link

Log4j have release 2.24.2 solving apache/logging-log4j2#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

@wilkinsona
Copy link
Member

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.

@wilkinsona wilkinsona closed this as not planned Won't fix, can't repro, duplicate, stale Nov 28, 2024
@wilkinsona wilkinsona removed the status: waiting-for-triage An issue we've not yet triaged label Nov 28, 2024
@YanivKunda
Copy link
Author

Sorry, it was my mistake not reading the template all the way through...
Thanks for the fail-fast response!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants