If there are commit.lock files being left over, you should really investigate why that is happening. Something is probaly dying, and you are not catching it and cleaning up by closing things like IndexReader or IndexWriter. If you want to forcefully unlock the index, use isLocked and unlock methods in IndexWriter. Not recommended, though.
Otis --- Supun Edirisinghe <[EMAIL PROTECTED]> wrote: > Hi everybody, I'm new to the mail list. > > I'm also new to using Lucene. > > We use lucene to index some of our pages. > > sometimes (for a reason unknown to us) a commit.lock file is left and > > searches using the index don't work. > > what are some of the causes for this commit.lock file to persist. > > I've read in the faq that it is written so that access to the > segments > is synchronized correctly. > > What are some good strategies to make make this file go away? Would > it > be a good idea to assign a program to just check the timestamp on > that file and just delete it if it has been there for a long time? > > all comments are welcome. > > thanks > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
