Likely your exception happened because a reader was trying to open just as a writer was committing, twice in a row.
Do you commit (flush or close) frequently from your writer? As of 2.1, Lucene no longer uses a commit locks -- commits are now lockless, so you won't hit this on upgrading to 2.4. Mike On Wed, Apr 8, 2009 at 3:40 PM, Zhang, Lisheng <lisheng.zh...@broadvision.com> wrote: > Hi, > > Sorry that my initial message is not clear, I read lucene source code (both > 1.4.3 > and 2.4.0), and understood more. > > The problem is that when using lucene 1.4.3 sometimes when searching, we got > the error: > > Lock obtain timed out: > Lock@/tmp/lucene-ba94511756a2670adeac03a50532c63c-commit.lock > > It seems that in 2.4.0 we will never have this issue because this error can > only > happen when concurrent writing. > > Is this true? > > Thanks very much for helps, Lisheng > > >> -----Original Message----- >> From: Zhang, Lisheng >> Sent: Wednesday, April 08, 2009 9:08 AM >> To: 'java-user@lucene.apache.org' >> Subject: Lucene 1.4.3: Error when creating Searcher >> >> Hi, >> >> We are using lucene 1.4.3, sometimes when two threads try to search, >> one thread got error when creating MultiSearcher: >> >> Lock obtain timed out: >> Lock@/tmp/lucene-ba94511756a2670adeac03a50532c63c-commit.lock >> >> I read lucene FAQ and searched previous discussions, it seems that this >> error should be related to indexing, but we are only creating Searcher? >> >> Thanks very much for helps, Lisheng >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
