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

Ralph Goers edited comment on LOG4J2-2909 at 9/16/20, 3:17 PM:
---------------------------------------------------------------

Neither of those jars will contain the class that is showing up as the 
"offender" in JProfiler. You either have a jar named log4j-1.2.x.jar (where x 
is the minor version number) or you have log4j-1.2-api.jar which comes from 
Log4j 2 as a way to bridge from Log4j 1 to Log4j 2. 

What version of the JDK is your application running with?


was (Author: [email protected]):
Neither of those jars will contain the class that is showing up as the 
"offender" in JProfiler. You either have a jar named log4j-1.2.x.jar (where x 
is the minor version number) or you have log4j-1.2-api.jar which comes from 
Log4j 2 as a way to bridge from Log4j 1 to Log4j 2. 

> 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: Capture.PNG, JBoss4.2.3-log4j2.10.0.PNG, 
> JBoss4.2.3-log4j2.13.2.PNG, Log4jMethod.PNG, NonProblemLog4j2.10.0-part1.PNG, 
> NonProblemLog4j2.10.0-part2.PNG, NonProblemLog4j2.10.0-part3.PNG, 
> NonProblemLog4j2.10.0-part4.PNG, NonProblemLog4j2.10.0-part5.PNG, 
> NonProblemLog4j2.10.0-part6.PNG, ProblemLog4j2.13.2-part1.PNG, 
> ProblemLog4j2.13.2-part2.PNG, ProblemLog4j2.13.2-part3.PNG, 
> image-2020-08-31-14-54-27-974.png, log4j-api-2.10.0.jar, 
> log4j-api-2.13.2.jar, log4j-core-2.10.0.jar, log4j-core-2.10.0.jar, 
> log4j-core-2.13.2.jar, log4j-core-2.13.2.jar, log4j2 Configuration.xml
>
>
> 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)

Reply via email to