You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Gary Gregory (JIRA)" <ji...@apache.org> on 2018/10/02 14:29:00 UTC
[jira] [Commented] (LOG4J2-2462) OutOfMemory : AsyncLogger Threads
number increases under unknown circumstances
[ https://issues.apache.org/jira/browse/LOG4J2-2462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16635560#comment-16635560 ]
Gary Gregory commented on LOG4J2-2462:
--------------------------------------
[~Mokhtar],
You are using a very old version of Log4j, 2.7, can you try with the current version, 2.11.1?
Thank you,
Gary
> OutOfMemory : AsyncLogger Threads number increases under unknown circumstances
> ------------------------------------------------------------------------------
>
> Key: LOG4J2-2462
> URL: https://issues.apache.org/jira/browse/LOG4J2-2462
> Project: Log4j 2
> Issue Type: Bug
> Affects Versions: 2.7
> Environment: SOLARIS 10
> JVM Standard Edition (IBM build 1.8.0_111-b14 10_Nov_2016_21_59 solaris sparcv9(SR3 FP20+IV90630+IV90578))
> -DLog4jContextSelector=org.apache.logging.log4j.core.async.AsyncLoggerContextSelector
>
> Reporter: Bouraoui
> Priority: Major
> Attachments: Threads.png
>
>
> Hi,
> I have a strange behavior where my app goes OOM. when i analyse the heapdump, i find a lot of threads Log4j2-TF-XX-AsyncLogger having each 37Mo memory.
> I saw many issues related to this behavior , most of them fixed on 2.6
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)