[jira] [Commented] (LOG4NET-443) Logger.CallAppenders

2014-10-22 Thread Dominik Psenner (JIRA)
[ https://issues.apache.org/jira/browse/LOG4NET-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14179643#comment-14179643 ] Dominik Psenner commented on LOG4NET-443: - Or maybe you could try to use several

[jira] [Commented] (LOG4NET-443) Logger.CallAppenders

2014-10-21 Thread Dominik Psenner (JIRA)
[ https://issues.apache.org/jira/browse/LOG4NET-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178323#comment-14178323 ] Dominik Psenner commented on LOG4NET-443: - This could be indeed an orphaned lock

[jira] [Commented] (LOG4NET-443) Logger.CallAppenders

2014-10-21 Thread Calin Pavel (JIRA)
[ https://issues.apache.org/jira/browse/LOG4NET-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178338#comment-14178338 ] Calin Pavel commented on LOG4NET-443: - It's a Win 2008 R2 x64 Logger.CallAppenders

[jira] [Commented] (LOG4NET-443) Logger.CallAppenders

2014-10-21 Thread Dominik Psenner (JIRA)
[ https://issues.apache.org/jira/browse/LOG4NET-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178457#comment-14178457 ] Dominik Psenner commented on LOG4NET-443: - Then this one might be hitting you