Cannot open in read-only mode if write.lock is present about luke HOT 4 CLOSED

I have the same problem.

I had the same problem. After the index creation I had many different files in 
my index folder (*.fdt, *.fdx, *.tvf, *.tvx, etc.). Whet I tried to open the 
index, there always came an error.
Then I created the index once more AND did "myIndexWriter.close()" at the end 
of the indexing process. After that I had ony 3 files in the index folder 
(_0.cfs, semgents.gen, segments_2) and I could open the index with Luke without 
any errors.
Hope that helps you (or others with this issue?).

This behavior of Lucene and Luke is as designed. It's there to prevent 
accidental index corruption if there is another process that is still writing 
to the index. Therefore it makes sense that it should require a write access 
and it should be a conscious decision that you really want to modify an 
existing index (unlocking is a modification).

Huh? Why does it make sense that it should require write access? I came across 
this when trying to read an index that was currently being written by another 
process.  I know you shouldn't have more than one concurrent writer, which is 
why I selected "Open in Read-Only mode".  Seems like Luke should allow 
read-only access to a locked index, since that's what Lucene is designed to 
support.