[ http://issues.apache.org/jira/browse/LUCENE-748?page=comments#action_12459489 ] Jed Wesley-Smith commented on LUCENE-748: -----------------------------------------
I guess, particularly in light of LUCENE-702 that this behavior is OK - and the IndexReader.unlock(dir) is a good suggestion. My real problem was that the finalize() method does eventually remove the write lock. For me then the suggestion would be to document the exceptional behavior of the close() method (ie. it means that changes haven't been written and the write lock is still held) and link to the IndexReader.unlock(Directory) method. > Exception during IndexWriter.close() prevents release of the write.lock > ----------------------------------------------------------------------- > > Key: LUCENE-748 > URL: http://issues.apache.org/jira/browse/LUCENE-748 > Project: Lucene - Java > Issue Type: Bug > Affects Versions: 1.9 > Environment: Lucene 1.4 through 2.1 HEAD (as of 2006-12-14) > Reporter: Jed Wesley-Smith > > After encountering a case of index corruption - see > http://issues.apache.org/jira/browse/LUCENE-140 - when the close() method > encounters an exception in the flushRamSegments() method, the index > write.lock is not released (ie. it is not really closed). > The writelock is only released when the IndexWriter is GC'd and finalize() is > called. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
