logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <garydgreg...@gmail.com>
Subject Re: Memory leak by not disposing loggers
Date Sun, 19 Apr 2015 16:27:06 GMT
The LoggerContext.loggers is a ConcurrentHashMap<String, Loggers>. It
sounds like you need the effect of a ConcurrentHashMap with weak values...

Gary

On Sun, Apr 19, 2015 at 2:27 AM, Veselin M <veselin_m84@yahoo.com.invalid>
wrote:

> Hello all,
>
> I have a memory leak problem with Log4j2. I’m using SLF4J to get loggers
> for my objects. Unfortunately when they get garbage collected the logger
> remains cached in LoggerContext.loggers in the log4j framework. Is there
> any way to prevent the caching or to remove the logger?
>
> Regards
> Veselin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>


-- 
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message