[
https://issues.apache.org/jira/browse/LOG4J2-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219619#comment-15219619
]
Remko Popma commented on LOG4J2-1340:
-------------------------------------
Yes, that is theoretically possible (although unlikely that your application
will actually log 250000 large messages in a row). This can be a problem if the
application logs a lot and the appender is slow (jdbc for example) so the ring
buffer fills up.
Also, you are correct that log4j will release (null out) the references in the
ringbuffer slot after the log event has been processed by the appender.
> 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
> Attachments: 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: [email protected]
For additional commands, e-mail: [email protected]
