You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "Akshay Kumar (Jira)" <ji...@apache.org> on 2023/05/11 17:10:00 UTC

[jira] [Created] (LOG4J2-3661) High Heap | GC Issue | Log4j 2 | Log4j1.x-2.x | Bridge

Akshay Kumar created LOG4J2-3661:
------------------------------------

             Summary: High Heap | GC Issue | Log4j 2 | Log4j1.x-2.x | Bridge
                 Key: LOG4J2-3661
                 URL: https://issues.apache.org/jira/browse/LOG4J2-3661
             Project: Log4j 2
          Issue Type: Bug
    Affects Versions: 2.17.2
            Reporter: Akshay Kumar
         Attachments: Screenshot 2023-05-11 at 9.21.55 PM.png, Screenshot 2023-05-11 at 9.22.43 PM.png

* We have migrated from log4j 1 to log4j 2 using the bridge approach in our Application.
 * We push the key-value pairs to print in logs as provided in the pattern layout with the help of NDC and MDC.
 * In log4j2 (bridge), this NDC internally uses ThreadContext to store the keys and values.
 * But it seems that there is some bug in the ThreadContext, as its stack keeps increasing in size causing a high heap due to which the application starts doing Full GC.
 * And the application become slow.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)