You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Ali Murtaza (Jira)" <ji...@apache.org> on 2020/08/13 13:54:00 UTC
[jira] [Updated] (LOG4J2-2909) Version Upgrade of log4j2 jars from
2.10.0 to 2.13.2 cause TPS degradation
[ https://issues.apache.org/jira/browse/LOG4J2-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ali Murtaza updated LOG4J2-2909:
--------------------------------
Attachment: log4j.PNG
Log4jMethod.PNG
Description:
Hi,
After updating the log4j2 jars from *2.10.0* to *2.13.2* in *TOMCAT 9.0.31* and *JBOSS 4.2.3* we are facing almost *40% TPS* degradation in our application.
Further Analysis shows that almost *28%* of total time is taken by log4j2 method.
!Log4jMethod.PNG!
was:
Hi,
After updating the log4j2 jars from *2.10.0* to *2.13.2* in *TOMCAT 9.0.31* and *JBOSS 4.2.3* we are facing almost *40% TPS* degradation in our application.
> Version Upgrade of log4j2 jars from 2.10.0 to 2.13.2 cause TPS degradation
> ---------------------------------------------------------------------------
>
> Key: LOG4J2-2909
> URL: https://issues.apache.org/jira/browse/LOG4J2-2909
> Project: Log4j 2
> Issue Type: Bug
> Components: Log4j-Audit
> Affects Versions: 2.13.2
> Reporter: Ali Murtaza
> Priority: Critical
> Fix For: 2.10.0
>
> Attachments: Log4jMethod.PNG, log4j.PNG
>
>
> Hi,
> After updating the log4j2 jars from *2.10.0* to *2.13.2* in *TOMCAT 9.0.31* and *JBOSS 4.2.3* we are facing almost *40% TPS* degradation in our application.
> Further Analysis shows that almost *28%* of total time is taken by log4j2 method.
> !Log4jMethod.PNG!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)