I encountered the famous AIOOBE:
java.lang.ArrayIndexOutOfBoundsException: 207243
at org.apache.lucene.util.BitVector.get(BitVector.java:63)
at org.apache.lucene.index.SegmentTermDocs.next
(SegmentTermDocs.java:110)
at org.apache.lucene.index.SegmentTermDocs.skipTo
(SegmentTermDocs.java:194)
at org.apache.lucene.index.MultiTermDocs.skipTo
(MultiReader.java:421)
at org.apache.lucene.search.TermScorer.skipTo
(TermScorer.java:144)
at org.apache.lucene.search.ReqExclScorer.toNonExcluded
(ReqExclScorer.java:82)
at org.apache.lucene.search.ReqExclScorer.next
(ReqExclScorer.java:61)
at org.apache.lucene.search.BooleanScorer2.score
(BooleanScorer2.java:290)
at org.apache.lucene.search.IndexSearcher.search
(IndexSearcher.java:132)
at org.apache.lucene.search.Searcher.search
(Searcher.java:116)
It seems that this MAY be caused when using MemoryMapped files and a
disk error occurs. The index is constant. Every time the error occurs
I get the following error message in the Windows system event log:
An error was detected on device \Device\Harddisk0 during a paging
operation.
For more information, see Help and Support Center at http://
go.microsoft.com/fwlink/events.asp.
Could it be that when using a MemoryMapped file that disk read errors
are not propagated, only to appears are corrupted data later (invalid
document #)?
