You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/12/23 20:17:00 UTC

[jira] [Work logged] (LOG4J2-2415) Lock contention in classloader because of missing org.slf4j.ext.EventData

     [ https://issues.apache.org/jira/browse/LOG4J2-2415?focusedWorklogId=362701&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-362701 ]

ASF GitHub Bot logged work on LOG4J2-2415:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 23/Dec/19 20:16
            Start Date: 23/Dec/19 20:16
    Worklog Time Spent: 10m 
      Work Description: turbanoff commented on pull request #324: LOG4J2-2415 - Lock contention in classloader because of missing org.slf4j.ext.EventData
URL: https://github.com/apache/logging-log4j2/pull/324
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 362701)
    Remaining Estimate: 0h
            Time Spent: 10m

> Lock contention in classloader because of missing org.slf4j.ext.EventData
> -------------------------------------------------------------------------
>
>                 Key: LOG4J2-2415
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2415
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: SLF4J Bridge
>    Affects Versions: 2.11.0
>            Reporter: Andrey Turbanov
>            Priority: Major
>         Attachments: LOG4J2-2415.patch, screenshot-1.png
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Recently I found one of lock contention and performance problem in our application.
> As you can see it happens because we don't have {{org.slf4j.ext.EventData}} class in classpath, but slf4j bridge tries to load it on every Logger creation.
> {noformat}
> Class java.lang.ClassLoader.loadClass(java.lang.String, boolean)
>    Class sun.misc.Launcher$AppClassLoader.loadClass(java.lang.String, boolean)
>       Class java.lang.ClassLoader.loadClass(java.lang.String)
>          Class org.apache.logging.log4j.util.LoaderUtil.loadClass(java.lang.String)
>             EventDataConverter org.apache.logging.slf4j.Log4jLogger.createConverter()
>                void org.apache.logging.slf4j.Log4jLogger.<init>(org.apache.logging.log4j.spi.ExtendedLogger, java.lang.String)
>                   Logger org.apache.logging.slf4j.Log4jLoggerFactory.newLogger(java.lang.String, org.apache.logging.log4j.spi.LoggerContext)
>                      Object org.apache.logging.slf4j.Log4jLoggerFactory.newLogger(java.lang.String, org.apache.logging.log4j.spi.LoggerContext)
>                         Object org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(java.lang.String)
>                            Logger org.apache.logging.slf4j.Log4jLoggerFactory.getLogger(java.lang.String)
>                               Logger org.slf4j.LoggerFactory.getLogger(java.lang.String)
>                                  void com.devexperts.dxcore.api.AccountGroupsCacheImpl.<init>()
> {noformat}
>  !screenshot-1.png! 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)