You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Remko Popma (JIRA)" <ji...@apache.org> on 2016/12/16 00:04:59 UTC
[jira] [Resolved] (LOG4J2-1340) AsyncLogger's Ringbuffer holding
all JVM memory
[ https://issues.apache.org/jira/browse/LOG4J2-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Remko Popma resolved LOG4J2-1340.
---------------------------------
Resolution: Not A Problem
Assignee: Remko Popma
Resolving this issue as "not a problem". Please reopen if more follow up is required.
> AsyncLogger's Ringbuffer holding all JVM memory
> -----------------------------------------------
>
> Key: LOG4J2-1340
> URL: https://issues.apache.org/jira/browse/LOG4J2-1340
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.5
> Environment: Linux 2.6.32-431.17.1.el6.x86_64 x86_64
> java version "1.7.0_75"
> OpenJDK Runtime Environment (rhel-2.5.4.0.el6_6-x86_64 u75-b13)
> OpenJDK 64-Bit Server VM (build 24.75-b04, mixed mode)
> Reporter: Soma
> Assignee: Remko Popma
> Attachments: debuglog ringbuffersize.png, heapdump.JPG
>
>
> JVM getting Out of memory. when I see the heapdump analysis I found 93% of memory occupied by AsyncLogger's RingBuffer. we have total of 5 AsyncLoggers in our applications each having default buffer size.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org