[
https://issues.apache.org/jira/browse/LOG4NET-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741982#action_12741982
]
Thomas Haller commented on LOG4NET-225:
---------------------------------------
thank you for reviewing my Code!
yeah thats allright - i have overseen that!!
in the reall time Application i have a LEVEL=WARN filter on that appender,
and thread #2 is only logging Debug.
so this would not be a problem within my scenario.
hmmm maybe i can pass some info to the new thread to avoid reentrency...
> 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.
