Nicko, On 6/3/05, Nicko Cadell <[EMAIL PROTECTED]> wrote: > > The <lockingModel> is only supported in log4net 1.2.9 and above. In > 1.2.0 Beta 8 the output file is being locked exclusively by the first > appender to be configured. Can you try upgrading to 1.2.9 which has > support for the file appender locking models.
I did some fairly extensive testing on a similar problem. In our case, I found that the problem was caused by having another program reading (tailing) the file as it was being written. The root of the problem turned out to be that the READING program (i.,e., NOT the log4NET appender) needed to share the file using a sharing attribute FILE_SHARE_DELETE (allowing another program to delete the file that's being read) so that the rollingfileAppender could rename the file. Unfortunately, this attribute is only documented in some of the functions that can be used in a native environment and doesn't seem to be included in the .NET framework. This is unfortunate as I understand it was originally intended to improve Unix compatibility. I suppose that the bottom line is that the file "appender locking models" improvement helps but doesn't eliminate the problem. -- Mike Blake-Knox
