[jira] [Updated] (LOG4J2-1457) Class loader deadlock when using async logging and extended stack trace pattern

2016-09-08 Thread Matt Sicker (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-1457: Summary: Class loader deadlock when using async logging and extended stack trace pattern (was:

[jira] [Updated] (LOG4J2-1457) Class loader deadlock when using async logging

2016-07-18 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1457: Fix Version/s: 2.7 I assume we want to include this in the next release so I've set the fix

[jira] [Updated] (LOG4J2-1457) Class loader deadlock when using async logging

2016-07-11 Thread Leon Finker (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leon Finker updated LOG4J2-1457: Attachment: LOG4J2-1457.patch Hi Gary, please review LOG4J2-1457.patch Thank you > Class loader

Re: [jira] [Updated] (LOG4J2-1457) Class loader deadlock when using async logging

2016-07-06 Thread Leon Finker
This application doesn't create any other class loaders besides the standard. It's regular JVM app (not tomcat or any other hosted process). According to: http://docs.oracle.com/javase/7/docs/technotes/guides/lang/cl-mt.html The class loading lock is done on class loader + class name since

Re: [jira] [Updated] (LOG4J2-1457) Class loader deadlock when using async logging

2016-07-06 Thread Ralph Goers
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 wrote: > > Although I'm still not clear why it deadlocks. I can confirm the thread

Re: [jira] [Updated] (LOG4J2-1457) Class loader deadlock when using async logging

2016-07-06 Thread Leon Finker
Although I'm still not clear why it deadlocks. I can confirm the thread in is logging an exception. But if the AsyncLogger thread picked up this same event (assumption), why the thread in doesn't continue... On 2016-07-06 10:57 (-0400), "Leon Finker (JIRA)" wrote: > >

[jira] [Updated] (LOG4J2-1457) Class loader deadlock when using async logging

2016-07-06 Thread Leon Finker (JIRA)
[ 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 >