[
https://issues.apache.org/jira/browse/LOG4J2-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17087421#comment-17087421
]
Riya Reji commented on LOG4J2-2792:
-----------------------------------
We were using open JDK 11 with log4j 2.11.0 from June 2019. We never faced any
performance issues with 2.11.0 log4j jar.
But when we upgraded to 2.13.0 we started facing performance issues. We
initially verified our code and couldn't find any issues. Then we started
looking for the jars we have upgraded and found that log4j 2.13.0 was causing
performance issues. We tried using 2.12.1 and 2.12.0 ,but faced the same issue.
So we have downgraded to 2.11.0. Is there any major change from 2.11.0 to
2.12.0/2.12.1/2.13.0 as 2.11.0 is not causing any performance issues with JDK
11?
Log4j2.xml is already shared in this thread. Please let me know if any more
information is required.
> Performance issue in log4j 2.12.1 and log4j 2.13.0
> --------------------------------------------------
>
> Key: LOG4J2-2792
> URL: https://issues.apache.org/jira/browse/LOG4J2-2792
> Project: Log4j 2
> Issue Type: Bug
> Components: API, Core
> Affects Versions: 2.12.1, 2.13.0
> Environment: System configuration: Redhat Linux 7,12-core,16Gb RAM
> Application server: Apache tomcat 9.0.16
> Reporter: Riya Reji
> Priority: Blocker
> Attachments: 24-jstack-2020-02-23-173500.zip, log4j2.xml,
> log4j_2_13_CPU_SPIKE.PNG
>
>
> Hi,
> When log4j2 was upgraded from 2.11.0 to 2.12.1 or 2.13.0,the cpu utilization
> was spiking to 100 %. When 2.11.0 version was used the CPU utilization was
> below 40%.
>
> PFA image of CPU utilization when 2.13.0 was used
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
