is it related to issue https://issues.apache.org/jira/browse/LOG4J2-1221
On Tue, Apr 5, 2016 at 12:52 PM, Soma (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/LOG4J2-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15225817#comment-15225817 > ] > > Soma commented on LOG4J2-1340: > ------------------------------ > > I see most of the threads waiting to publish event to buffer(default > buffers size and wait strategy)even though application logs less number of > logs. is it because of buffer slots full or any other reasons? > > "http-bio-8080-exec-484" - Thread t@3383 > java.lang.Thread.State: TIMED_WAITING > at sun.misc.Unsafe.park(Native Method) > at > java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:338) > at > com.lmax.disruptor.MultiProducerSequencer.next(MultiProducerSequencer.java:136) > at > com.lmax.disruptor.MultiProducerSequencer.next(MultiProducerSequencer.java:105) > at com.lmax.disruptor.RingBuffer.publishEvent(RingBuffer.java:502) > at > org.apache.logging.log4j.core.async.AsyncLoggerConfigDisruptor.enqueue(AsyncLoggerConfigDisruptor.java:270) > at > org.apache.logging.log4j.core.async.AsyncLoggerConfigDisruptor.enqueueEvent(AsyncLoggerConfigDisruptor.java:252) > at > org.apache.logging.log4j.core.async.AsyncLoggerConfigDisruptor.tryCallAppendersInBackground(AsyncLoggerConfigDisruptor.java:232) > at > org.apache.logging.log4j.core.async.AsyncLoggerConfig.callAppenders(AsyncLoggerConfig.java:96) > at > org.apache.logging.log4j.core.config.LoggerConfig.processLogEvent(LoggerConfig.java:378) > at > org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:362) > at > org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:352) > at > org.apache.logging.log4j.core.config.AwaitCompletionReliabilityStrategy.log(AwaitCompletionReliabilityStrategy.java:63) > at org.apache.logging.log4j.core.Logger.logMessage(Logger.java:147) > at > org.apache.logging.log4j.spi.AbstractLogger.logMessage(AbstractLogger.java:1022) > at > org.apache.logging.log4j.spi.AbstractLogger.logIfEnabled(AbstractLogger.java:980) > at org.apache.logging.log4j.spi.AbstractLogger.info > (AbstractLogger.java:679) > > > > > 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] > > -- Regards, Sampath
