You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Remko Popma (JIRA)" <ji...@apache.org> on 2015/10/18 16:01:05 UTC

[jira] [Commented] (LOG4J2-1116) upgrade to log4j2 causes too frequent minor gc

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

Remko Popma commented on LOG4J2-1116:
-------------------------------------

As Ralph said, can you please provide your log4j 2 configuration file, your GC log and your JVM parameters, and some indication on how many lines per minute your app is logging when this happens. We cannot help you without more information.

> upgrade to log4j2 causes too frequent minor gc
> ----------------------------------------------
>
>                 Key: LOG4J2-1116
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1116
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.3
>         Environment: jdk1.6 
> slf4j 1.7.9
> log4j2.3
>            Reporter: Mingjiang Shi
>            Priority: Critical
>
> We used slf4j+log1.2 in our spring web application. Due to the log4j1.0 performance issue, we upgrade it to log4j2. When it goes to production, it experienced very frequent minor gc (once per second) even though the eden area is not full. For example, the eden area just occupied 10%, the minor gc also happens. The issue disappears when rolling back to log4j1.2. 
> Can anyone show some hints on diagnose this issue? Thanks!



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