logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leon Finker (JIRA)" <j...@apache.org>
Subject [jira] [Created] (LOG4J2-1457) Class loader deadlock when using async logging
Date Wed, 06 Jul 2016 14:53:11 GMT
Leon Finker created LOG4J2-1457:

             Summary: Class loader deadlock when using async logging
                 Key: LOG4J2-1457
                 URL: https://issues.apache.org/jira/browse/LOG4J2-1457
             Project: Log4j 2
          Issue Type: Bug
    Affects Versions: 2.6.1
         Environment: On CentOS 6.7 and Java 1.8.0_60.
            Reporter: Leon Finker
            Priority: Critical

We've encountered a class loading deadlock. Please review attached thread dump. Is it possible
to have an option of pre-initializing the exception's thread stack on the caller's thread?
It's hard to predict what libraries are doing in their classes' static initializers and may
eventually end up logging and causing deadlock.

In the attached thread dump here are the threads of interest:
"Log4j2-AsyncLogger[AsyncContext@18b4aac2]1" #16 daemon prio=5 os_prio=0 tid=0x00007ff870c7b000
nid=0x79f3 in Object.wait() [0x00007ff839142000]
   java.lang.Thread.State: RUNNABLE
        at java.lang.Class.forName0(Native Method)
"1A03340:Company:japan" #568 prio=5 os_prio=0 tid=0x00007ff871677000 nid=0x725 runnable [0x00007ff74bd27000]

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message