[prev in list] [next in list] [prev in thread] [next in thread] 

List:       log4j-dev
Subject:    [jira] [Updated] (LOG4J2-1340) AsyncLogger's Ringbuffer holding all JVM memory
From:       "Soma (JIRA)" <jira () apache ! org>
Date:       2016-03-31 6:51:25
Message-ID: JIRA.12954874.1459406891000.97708.1459407085503 () Atlassian ! JIRA
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/LOG4J2-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Soma updated LOG4J2-1340:
-------------------------
    Attachment: heapdump.JPG

> 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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]