Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is there a way to force a Log4j Logger to be released/garbage collected?
In general, does Log4j “hang on” to Logger references in some static collection?
I see the Logger.shutdown() method, which is deprecated and refers to LoggerManager.shutdown(), which doesn’t sound like it addresses a single Logger instance.
You could take a look at the log4j source code yourself.
Based on a quick trawl, I think the answers are:
Not with that level of granularity. The only thing I could find was a method (
Heirarchy.clear()) that releases all loggers … and destroy the logging hierarchy in the process.Yes. And the collection doesn’t use weak references …