AW: AppenderSkeletion lock in DoAppend

2015-03-05 Thread Dominik Psenner
Taking this to log4net dev since this goes well beyond the usage of log4net, too. Logs are typically written by software that is programmed, aren’t they? Thus one could happen to recursively trying to log something in his source code without being aware of it. Maybe the example was not

AW: AppenderSkeletion lock in DoAppend

2015-03-04 Thread Dominik Psenner
Hi, from what I can recall it could happen that the formatted representation of a logging event gets mixed up with data from other events and thus the characters streamed to a sink become garbage (i.e. a file, console, ..) if this lock is removed. Internally a lot of things are cached

AW: AppenderSkeletion lock in DoAppend

2015-03-04 Thread Dominik Psenner
A log event might be badly programmed and recursive by definition. Think of two objects that try each to log while trying to format each other: A { DoWork() { Log(“A: {0}”, B) } } B { DoWork () { Log(“B: {0}”, A) } } I might be wrong, but something like that does the