Re: opening an IndexWriter for an exisiting index causing lock exception

2007-01-08 Thread S Edirisinghe
Thanks Mike, you are right. There was a really bad test method that didn't clean up after itself. Thanks for the heads up. This was not a Lucene problem, it was just me not going through all of the unit test methods. On 1/8/07, Michael McCandless <[EMAIL PROTECTED]> wrote: S Edirisinghe wrote:

Re: opening an IndexWriter for an exisiting index causing lock exception

2007-01-08 Thread Michael McCandless
S Edirisinghe wrote: I'm having a write lock problem when I try to open an existing index. When I try to open the index with the recreate set to false, I get this exception java.io.IOException: Lock obtain timed out: Lock@/tmp/lucene- e683c0b3e52b8094bba62b22617efd41-write.lock at org.apache

opening an IndexWriter for an exisiting index causing lock exception

2007-01-08 Thread S Edirisinghe
Hello, I'm having a write lock problem when I try to open an existing index. When I try to open the index with the recreate set to false, I get this exception java.io.IOException: Lock obtain timed out: Lock@/tmp/lucene- e683c0b3e52b8094bba62b22617efd41-write.lock at org.apache.lucene.store.L