You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Gary D. Gregory (Jira)" <ji...@apache.org> on 2020/08/13 19:05:00 UTC
[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=17177283#comment-17177283 ]
Gary D. Gregory edited comment on LOG4J2-2909 at 8/13/20, 7:04 PM:
-------------------------------------------------------------------
You can hopefully export this run, attach it here, so we can look at it in... which tool is this?
was (Author: garydgregory):
You probably export this run, attache it here, so we can look at it in... which tool is this?
> 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)