Can you provide a better example? If it didn't deadlock, it would run out of stack since you're calling your own appender recursively?
Regards, Dag -----Opprinnelig melding----- Fra: Thomas Haller (JIRA) [mailto:[email protected]] Sendt: 10. august 2009 17:28 Til: [email protected] Emne: [jira] Updated: (LOG4NET-225) Multithreading and Deadlocks [ https://issues.apache.org/jira/browse/LOG4NET-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Haller updated LOG4NET-225: ---------------------------------- Attachment: Log4NetDeadlock.zip project to reproduce that Problem > Multithreading and Deadlocks > ---------------------------- > > Key: LOG4NET-225 > URL: https://issues.apache.org/jira/browse/LOG4NET-225 > Project: Log4net > Issue Type: Bug > Components: Appenders > Affects Versions: 1.2.10 > Reporter: Thomas Haller > Priority: Blocker > Attachments: Log4NetDeadlock.zip > > > If an Appender has to execute some logic on another thread, > witch uses also log4net, this leads to a deadlock. > The sample project i created demonstrates that problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.f-secure.com/
