[
https://issues.apache.org/jira/browse/LUCENENET-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680913#action_12680913
]
Olivier Aboilard commented on LUCENENET-176:
--------------------------------------------
Hello there,
this looks more like a special use case.
As your live indexes are read-only, I just set this magic directive in the
Application_Start :
Lucene.Net.Store.FSDirectory.SetDisableLocks(true);
(Lucene in action p.66)
> write.lock file problem
> -----------------------
>
> Key: LUCENENET-176
> URL: https://issues.apache.org/jira/browse/LUCENENET-176
> Project: Lucene.Net
> Issue Type: Bug
> Environment: windows server 2003, .net v2 framework, IIS 6
> Reporter: Colin Robinson
>
> Hello,
> We daily get the below error, which causes w3wp.exe to crash and restart. I
> thought this maybe due to 2 application pools using the same lucene indexes
> but I changed this to just one app pool but the error still occurs? Any
> ideas or help would be great.
> System.IO.IOException was unhandled
> Message: The process cannot access the file
> 'C:\WINDOWS\TEMP\lucene-62db5567fbeaae16396e79fb8fe42895-write.lock' because
> it is being used by another process.
> Many thanks
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
