[
https://issues.apache.org/jira/browse/LOG4J2-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17188022#comment-17188022
]
Ralph Goers edited comment on LOG4J2-2909 at 8/31/20, 9:56 PM:
---------------------------------------------------------------
Well, rats. I thought I updated this. I sent you a direct email on Aug 26. Here
is what I sent:
I got your files and am looking at them. I was hoping they would be snapshots
I could use in YourKit but it doesn’t seem to support .jps files. I am not sure
what formats they have in common. I’ve downloaded the trial version of
JProfiler and will see what I can see but right off the bat its UI looks a bit
more challenging. It just isn’t showing me the level of detail I would expect.
It is not showing me any of the internal classes of Log4j. For example,
!image-2020-08-31-14-54-27-974.png!
This shows [Logger.info|http://logger.info/] supposedly calling RingBuffer
directly, but it doesn’t. I need to see the details of Log4j. Does JProfiler
filter out org.apache classes by default? If so, please disable that.
was (Author: [email protected]):
Well, rats. I thought I updated this. I sent you a direct email. Here is what I
sent:
I got your files and am looking at them. I was hoping they would be snapshots I
could use in YourKit but it doesn’t seem to support .jps files. I am not sure
what formats they have in common. I’ve downloaded the trial version of
JProfiler and will see what I can see but right off the bat its UI looks a bit
more challenging. It just isn’t showing me the level of detail I would expect.
It is not showing me any of the internal classes of Log4j. For example,
!image-2020-08-31-14-54-27-974.png!
This shows [Logger.info|http://logger.info/] supposedly calling RingBuffer
directly, but it doesn’t. I need to see the details of Log4j. Does JProfiler
filter out org.apache classes by default? If so, please disable that.
> 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, 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)
