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

Log4j2 not working with Spring Boot 3.4.2 together with BlockHound #43963

Closed
micopiira opened this issue Jan 25, 2025 · 1 comment
Closed

Log4j2 not working with Spring Boot 3.4.2 together with BlockHound #43963

micopiira opened this issue Jan 25, 2025 · 1 comment
Labels
for: external-project For an external project and not something we can fix status: invalid An issue that we don't feel is valid

Comments

@micopiira
Copy link

When upgrading to Spring Boot 3.4.2 our logging stopped completely working.

After narrowing down I figured the problem happens with Spring Boot 3.4.2 when using Log4j2 together with BlockHound.

Here is a minimum reproducer repo: https://github.com/micopiira/spring-boot-log4j2-issue

Spring Boot 3.4.1 with exact same Log4j2 version and BlockHound version works.

Spring Boot 3.4.1:

Image

Spring Boot 3.4.2:

Image
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Jan 25, 2025
@wilkinsona
Copy link
Member

wilkinsona commented Jan 26, 2025

Thanks for the report and for the minimal sample. I assume that something has changed in Spring Boot 3.4.2 that is causing BlockHound to break Log4j2 in some way. Unfortunately, given that this works fine without BlockHound and the way in which BlockHound works, I don't think there's anything we can do about this in Spring Boot. Please raise a BlockHound issue so that they can investigate further.

@wilkinsona wilkinsona closed this as not planned Won't fix, can't repro, duplicate, stale Jan 26, 2025
@wilkinsona wilkinsona added status: invalid An issue that we don't feel is valid for: external-project For an external project and not something we can fix and removed status: waiting-for-triage An issue we've not yet triaged labels Jan 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for: external-project For an external project and not something we can fix status: invalid An issue that we don't feel is valid
Projects
None yet
Development

No branches or pull requests

3 participants