[
https://issues.apache.org/jira/browse/LOG4J2-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15225920#comment-15225920
]
Remko Popma commented on LOG4J2-1340:
-------------------------------------
Yes this looks like the buffer was full at the time your application called
{{logger.info(...)}}.
This is possible if the application threads keep adding log events faster than
the Appender can process them. The large buffer size helps to deal with bursts
of events, but if the sustained logging rate is faster than the Appender can
handle, you need to either produce less log events, or consume the log events
faster.
Out of interest, what Appender or Appenders do you have configured?
> 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]
