Skip to content

Conversation

@taranion
Copy link

This little patch solved the Log4J bridge problem for me. LogManager.getLogger(name) returns NULL, if the logger did not exist before - Logger.getLogger(name) does create an eventually not yet existing logger or returns the existing one.

Thank you for creating this project - it helps me preventing the bloat from full blown webserver frameworks.

@robaho
Copy link
Owner

robaho commented Aug 29, 2024

Thanks for the patch - I am glad the project is helping you.

I am not sure this change is correct though. I had added the utilities Logger for per instance logging, when the original code only used the System logger facilities - in order to change the filtering.

I am going to need to review the best way to fix this - I probably did something wrong. I normally only use the utility loggers, but I was trying to stay as close as possible to the original JDK httpserver code.

Are you certain your log4j is setup properly, and the System loggers are being redirected there?

@robaho
Copy link
Owner

robaho commented Aug 30, 2024

Thank you for the PR. After reviewing the apis your code change was correct, but I modified the PR slightly to remove the unused imports, and avoid white space changes.

@robaho robaho closed this Aug 30, 2024
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

Successfully merging this pull request may close these issues.

2 participants