lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Digy (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENENET-176) write.lock file problem
Date Thu, 12 Mar 2009 10:48:50 GMT

    [ https://issues.apache.org/jira/browse/LUCENENET-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681253#action_12681253
] 

Digy commented on LUCENENET-176:
--------------------------------

You are probably trying to open another IndexWriter without closing the first one. If so,
this is the normal behaviour of Lucene.Net , not a bug.

DIGY

> 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.


Mime
View raw message