System.IO.IOException: Lock obtain timed out - Problem indexing with lucene.net?

Anpanman,

It doesn't look like anything should've disrupted Lucene in what you've explained. The only thing I can think of is that the parent privileges could've been changed. The recent MS updates for XP screwed up one of my apps that writes to TEMP as well. I just had to reset the privs on the parent, and everything went back to working.

Might not be a 200 point answer, but it couldn't hurt to check it out just in case XP got you, too.

Ric

Thanks, Ric.
I was also thinking it was a problems of writing privileges, but the thing is that it doesn't happen to me on my development computer, only on the shared hosting provider. I've written them, but didn't get an answer yet.

It boils down to the ASP.NET account not having writing privileges. My hosting provider changed something and for a couple of weeks I can't upload files via web, can't use lucene, well can't do something that's very basic in a website!
I'm testing out another provider these days and hopefully will be changing very soon.

you get the points anyway, ric :)
It was an urgent matter...

Apparently it might also be the account called NETWORK SERVICE in .net 2.0 or whatever the application pool identity is running as, that needs modify/write permissions to the index and temp folders.

hi,
i too face this type of problems..at that time i delete the write.lock in that indexed folder.. this type of problem arises due to optimization. suppose if u delete a indexed file without any optimization, write.lock will occur..

better use
indexwriter.optimise();
indexwriter.close();

after deleting a index file...

hi,

if (IndexReader.IsLocked(indexingFolder))
{

Response.write("it is locked");
IndexReader.Unlock(FSDirectory.GetDirectory(indexingFolder));
}
else
{
Response.write("it is not locked");
}