lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Ahmed (JIRA)" <>
Subject [jira] [Commented] (LUCENE-91) IndexWriter ctor does not release lock on exception
Date Wed, 08 Jun 2011 05:56:58 GMT


Adam Ahmed commented on LUCENE-91:

The better place for the timeout fix would probably be in Lock.obtain(), where it should attempt
something similar to Lock.release() if a timeout occurs.

> IndexWriter ctor does not release lock on exception
> ---------------------------------------------------
>                 Key: LUCENE-91
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: core/index
>    Affects Versions: 1.2
>         Environment: Operating System: All
> Platform: All
>            Reporter: Alex Staubo
>            Assignee: Lucene Developers
> If IndexWriter construction fails with an exception, the write.lock lock is not
> released.
> For example, this happens if one tries to open an IndexWriter on an FSDirectory
> which does not contain an Lucene index. FileNotFoundException will be thrown by
>, after which the write lock will remain in
> the directory, and nobody can open the index.
> I have been using this pattern -- doing IndexWriter(..., false), catching
> FileNotFoundException and doing IndexWriter(..., true) -- in my code to
> initialize the index on demand, because the app never know if the index already
> exists.

This message is automatically generated by JIRA.
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message