I would suggest that you try to find out
who is locking the file.
A tool such as Handle (Freeware) will tell
you that in a split sec. (http://www.sysinternals.com/utilities/handle.html)
Then you can see if it is another instance
of log4net, or if it is someone/something trying to read the file. In the
latter case, if you're lucky, you just have to specify that the reader open the
file in read-only, shared mode and the blocking will be gone.
In any case, it is always a good idea to see
what the problem really is, before you do any changes.
/Göran
From: Ramaa Davanagere
[mailto:[EMAIL PROTECTED]
Sent: den 12 december 2005 13:45
To: 'Log4NET
User'
Subject: RE: how to handle this
error?
I don't want to
use "MinimalLocking". Any other ideas?
-Original Message-
From: Ramaa Davanagere
Sent: Monday, December 12, 2005
7:40 AM
To:
[email protected]
Subject: how to handle this error?
This error occurs once in a
while and I wonder if there is a way to handle it. I turned on log4net internal
debugging and this is what I see.
log4net:ERROR [RollingFileAppender] Unable to
acquire lock on file C:\Program Files\Mobius\logfiles\log4net\vdrconBOLog.log.
The process cannot access the file "C:\Program
Files\Mobius\logfiles\log4net\vdrconBOLog.log" because it is being used by
another process.
Is there a way to unlock
the file so that log4net can continue with its job? What are the other ways to
resolve this error?
Thanks
-Ramaa
