[org.apache.logging.log4j.core.async.RingBufferLogEventTranslator] (value
[org.apache.logging.log4j.core.async.RingBufferLogEventTranslator@6caf0677])
but failed to remove it when the web application was stopped. Threads are
going to be renewed over time to try and avoid a probable memory leak.
The nearest mention I
Attachments generally do not make it to the mailing lists. There is no leak
report attached to the email.
I think you are going to have to explain a little more as to what your
application was doing that would cause so many Console Appenders. While there
is a Default Configuration there is no
>> reconfiguration.
> >>
> >> Sent from my iPhone
> >>
> >>> On 2015/04/20, at 8:07, Gary Gregory wrote:
> >>>
> >>> Are loggers GC'd on a reconfigure?
> >>> Gary
> >>>
> >>> Origi
on.
>>
>> Sent from my iPhone
>>
>>> On 2015/04/20, at 8:07, Gary Gregory wrote:
>>>
>>> Are loggers GC'd on a reconfigure?
>>> Gary
>>>
>>> Original message ----
>>> From: Remko Popma
>>&g
gt; > On 2015/04/20, at 8:07, Gary Gregory wrote:
> >
> > Are loggers GC'd on a reconfigure?
> > Gary
> >
> > Original message
> > From: Remko Popma
> > Date: 04/19/2015 15:33 (GMT-08:00)
> > To: Log4J Users List
> >
04/19/2015 15:33 (GMT-08:00)
> To: Log4J Users List
> Subject: Re: Memory leak by not disposing loggers
>
> Loggers are not GC-ed until the whole logging subsystem is GC-ed. That is
> until your webapp is unloaded or standalone process is stopped.
> Is your app a webapp?
>
Are loggers GC'd on a reconfigure?
Gary
Original message
From: Remko Popma
Date: 04/19/2015 15:33 (GMT-08:00)
To: Log4J Users List
Subject: Re: Memory leak by not disposing loggers
Loggers are not GC-ed until the whole logging subsystem is GC-ed. That is until
> sounds like you need the effect of a ConcurrentHashMap with weak values...
>
> Gary
>
> On Sun, Apr 19, 2015 at 2:27 AM, Veselin M
> wrote:
>
>> Hello all,
>>
>> I have a memory leak problem with Log4j2. I’m using SLF4J to get loggers
>> for my
The LoggerContext.loggers is a ConcurrentHashMap. 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
wrote:
> Hello all,
>
> I have a memory leak problem with Log4j2. I’m using SLF4J to get loggers
> fo
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
gt; checkThreadLocalMapForLeaks
>> SEVERE: The web application [/clearing-newcdev10] created a ThreadLocal
>> with key of type [java.lang.ThreadLocal] (value
>> [java.lang.ThreadLocal@131d70a]) and a value of type [
>> org.apache.logging.log4j.core.async.Async
adLocal
> with key of type [java.lang.ThreadLocal] (value
> [java.lang.ThreadLocal@131d70a]) and a value of type [
> org.apache.logging.log4j.core.async.AsyncLogger.Info] (value
> [org.apache.logging.log4j.core.async.AsyncLogger$Info@11cd743]) but
> failed to remove it when the web application was stopped. Threads are going
&
failed
to remove it when the web application was stopped. Threads are going to be
renewed over time to try and avoid a probable memory leak.
*Now JConsole has two thread *
*Name: AsyncLoggerConfig-1*
State: TIMED_WAITING
Total blocked: 0 Total waited: 307,234
Stack trace:
sun.misc.Unsafe.park
BUG No AsyncLogger.ExceptionHandler specified
> 2014-04-10 12:56:09,203 DEBUG Starting AsyncLogger disruptor with
> ringbuffer size 262144...
>
> SEVERE: The web application [/app] created a ThreadLocal with key of type
> [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@17b3a1e]) an
ava.lang.ThreadLocal] (value [java.lang.ThreadLocal@17b3a1e]) and a value
of type [org.apache.logging.log4j.core.async.AsyncLogger.Info] (value
[org.apache.logging.log4j.core.async.AsyncLogger$Info@1aca2de]) but failed
to remove it when the web application was stopped. Threads are going to be
renewed over time to try and avoid a probable
der
> clearReferencesThreads
> SEVERE: The web application [/app] appears to have started a thread named
> [AsyncLogger-1] but has failed to stop it. *This is very likely to create a
> memory leak.*
> Apr 08, 2014 12:32:17 PM org.apache.catalina.loader.WebappClassLoade
named
[AsyncLogger-1] but has failed to stop it. *This is very likely to create a
memory leak.*
Apr 08, 2014 12:32:17 PM org.apache.catalina.loader.WebappClassLoader
checkThreadLocalMapForLeaks
SEVERE: The web application [/app] created a ThreadLocal with key of type
[java.lang.ThreadLocal] (value
Hi,
For every new category created a new entry is added into
org.apache.log4j.Hierarchy.ht. And at the same time also for any
possible parent category of that new entry.
This cache is fine when you have a fairly fixed number possible
categories. That cache will grow to some size and remain
Thanks so far...
This may be possible, hough the heap from the coredump wasn't showing
many EJBs there. And I've asked to get me a stacktrace from the
coredump, to see in which context NDC was refereenced.
But I will also check our advice with EJB's being not properly
finalized, that could b
Sounds like the contextual information isn't being popped off the stack -
ensure your EJBs are being properly finalised and destroyed.
Regards,
Michael Erskine.
-
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
20 matches
Mail list logo
