[
https://issues.apache.org/jira/browse/LOG4J2-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14972423#comment-14972423
]
Remko Popma commented on LOG4J2-869:
------------------------------------
Sorry for the very late response.
When does this happen? If only at reconfiguration then it won't impact the
performance of your app, will it?
> Monitor contention at org.apache.logging.log4j.core.util.Loader.*
> -----------------------------------------------------------------
>
> Key: LOG4J2-869
> URL: https://issues.apache.org/jira/browse/LOG4J2-869
> Project: Log4j 2
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.0.1, 2.0.2, 2.1
> Reporter: Lucas Pouzac
> Labels: concurrency, performance
> Attachments: monitor_contention_log4j.png
>
>
> Loader.initializeClass() / Loader.loadClass() indirectly calls
> Class.forName0(), which calls into JRE lib method causing monitor contention.
> See screen shot
> Fix by caching values returned by Class.forName() in a static ConcurrentMap
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
