[
https://issues.apache.org/jira/browse/LOG4J2-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17198666#comment-17198666
]
Ralph Goers edited comment on LOG4J2-2909 at 9/19/20, 6:14 AM:
---------------------------------------------------------------
I will say it one more time. Log4j 2's log4j-api and log4j-core jars do not
contain the org.apache.log4j.Logger class. It is only found in the original
log4j 1 jar (log4j-1.2.x) or Log4j 2's compatibility jar (log4j-1.2-api). SLF4J
also provides a log4j-over-slf4j jar to route the Log4j API to SLF4J. It may
also be possible that your somehow have your own implementation of the log4j
1.x classes.
I am not sure why you are saying your Solaris machine is running a very old jdk
- Java 8 is still quite common. I do not understand why you cannot use YourKit
with Java 8. It is very well supported and I use it all the time. Without the
information that tells me what classes are actually involved I am afraid I am
going to have to close this issue.
was (Author: [email protected]):
I will say it one more time. Log4j 2's log4j-api and log4j-core jars do not
contain the org.apache.log4j.Logger class. It is only found in the original
log4j 1 jar (log4j-1.2.x) or Log4j 2's compatibility jar (log4j-1.2-api). SLF4J
also provides a log4j-over-slf4j jar to route the Log4j API to SLF4J. It may
also be possible that your somehow have your own implementation of the log4j
1.x classes.
I do not understand why you cannot use YourKit with Java 8. It is very well
supported and I use it all the time. Without the information that tells me
what classes are actually involved I am afraid I am going to have to close this
issue.
> 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)
