You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Lucas Pouzac (JIRA)" <ji...@apache.org> on 2014/10/06 17:12:34 UTC
[jira] [Updated] (LOG4J2-869) Monitor contention at
org.apache.logging.log4j.core.util.Loader.*
[ https://issues.apache.org/jira/browse/LOG4J2-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lucas Pouzac updated LOG4J2-869:
--------------------------------
Attachment: monitor_contention_log4j.png
> 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
> Fix For: 2.0.2, 2.1
>
> 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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org