Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Developers List" <log4j-dev@logging.apache.org>
Date: Wed, 6 Apr 2016 05:24:25 +0000 (UTC)
From: "Remko Popma (JIRA)" <jira@apache.org>
To: log4j-dev@logging.apache.org
Message-ID: <JIRA.12954874.1459406891000.147031.1459920265596@Atlassian.JIRA>
In-Reply-To: <JIRA.12954874.1459406891000@Atlassian.JIRA>
References: <JIRA.12954874.1459406891000@Atlassian.JIRA>
 <JIRA.12954874.1459406891293@arcas>
Subject: [jira] [Comment Edited] (LOG4J2-1340) AsyncLogger's Ringbuffer
 holding all JVM memory
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/LOG4J2-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15227742#comment-15227742 ] 

Remko Popma edited comment on LOG4J2-1340 at 4/6/16 5:24 AM:
-------------------------------------------------------------

I think you are trying to set the system property after Log4j has been initialized. The Spring configuration file is probably not the best place to do this.

Where to do this depends on the web container you are using. In Tomcat for example you would specify system properties in this file: {{$\{TOMCAT_HOME}\conf\catalina.properties}}. For other web containers please consult the container docs.

Instead of using system properties, the property can also be specified in a file named {{log4j2.component.properties}} by including this file in the classpath of the application.


was (Author: remkop@yahoo.com):
I think you are trying to set the system property after Log4j has been initialized. The Spring configuration file is probably not the best place to do this.

Where to do this depends on the web container you are using. In Tomcat for example you would specify system properties in this file: {{$\{TOMCAT_HOME}\conf\catalina.properties}}. For other web containers please consult the container docs.

> 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: 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