Do you know what the exception is and where it originated from? Does it correlate in any way to the other threads that are marked as runnable?
Ralph > On Jul 6, 2016, at 8:14 AM, Leon Finker <leon...@gmail.com> wrote: > > Although I'm still not clear why it deadlocks. I can confirm the thread in > <clinit> is logging an exception. But if the AsyncLogger thread picked up > this same event (assumption), why the thread in <clinit> doesn't continue... > > On 2016-07-06 10:57 (-0400), "Leon Finker (JIRA)" <j...@apache.org> wrote: >> >> [ >> https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel >> ] >> >> Leon Finker updated LOG4J2-1457: >> -------------------------------- >> Attachment: threaddump.txt >> >>> 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 >>> Attachments: threaddump.txt >>> >>> >>> 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) >>> ... >>> and >>> "1A03340:Company:japan" #568 prio=5 os_prio=0 tid=0x00007ff871677000 >>> nid=0x725 runnable [0x00007ff74bd27000] >>> ...<clinit>... >> >> >> >> -- >> This message was sent by Atlassian JIRA >> (v6.3.4#6332) >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org >> For additional commands, e-mail: log4j-dev-h...@logging.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-dev-h...@logging.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
