|
Now and then, log4net indicates a read error. When this happens, I immediately stop the logging application to inspect the line that log4net reports to be the problem. This line is always well formed. In fact, the whole file is well formed. This is proven by restarting log4net, and the logging file is then read without any complaints or read errors.
Any ideas what may cause this problem?
We are using log4net with the following layout pattern %date♥[%thread]♥%-5level♥%logger♥%message♥%exception♥%newline");
The "hearts" are 0x03 to avoid using delimiters that are part of the logging message itself.
We are using ...%exception♥%newline and not the other way around to allow for embedded newlines in the logging message itself.
Any help would be much appreciated.
|