This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 188557 - AIOOBE from NexusRepositoryIndexerImpl
Summary: AIOOBE from NexusRepositoryIndexerImpl
Status: RESOLVED WORKSFORME
Alias: None
Product: projects
Classification: Unclassified
Component: Maven (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: Antonin Nebuzelsky
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-10 16:38 UTC by CepO
Modified: 2010-11-18 14:06 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 164987


Attachments
stacktrace (2.98 KB, text/plain)
2010-07-10 16:38 UTC, CepO
Details
stacktrace (2.98 KB, text/plain)
2010-07-10 19:03 UTC, CepO
Details

Note You need to log in before you can comment on or make changes to this bug.
Description CepO 2010-07-10 16:38:05 UTC
Build: NetBeans IDE Dev (Build 201007090001)
VM: Java HotSpot(TM) Client VM, 16.0-b13, Java(TM) SE Runtime Environment, 1.6.0_18-b07
OS: Windows 7

User Comments:
GUEST: Performing latest plugin update.




Stacktrace: 
java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 38148
   at org.apache.lucene.util.BitVector.get(BitVector.java:91)
   at org.apache.lucene.index.SegmentTermDocs.next(SegmentTermDocs.java:125)
   at org.apache.lucene.index.DocumentsWriter.applyDeletes(DocumentsWriter.java:956)
   at org.apache.lucene.index.DocumentsWriter.applyDeletes(DocumentsWriter.java:918)
   at org.apache.lucene.index.IndexWriter.applyDeletes(IndexWriter.java:4339)
   at org.apache.lucene.index.IndexWriter.doFlush(IndexWriter.java:3579)
Comment 1 CepO 2010-07-10 16:38:10 UTC
Created attachment 100745 [details]
stacktrace
Comment 2 CepO 2010-07-10 19:03:15 UTC
Created attachment 100748 [details]
stacktrace
Comment 3 Jesse Glick 2010-11-16 22:26:32 UTC
Do you know much about Lucene usage?
Comment 4 Antonin Nebuzelsky 2010-11-18 14:06:45 UTC
Could be caused by corrupted index files, or by a bug in lucene or its usage by nexus indexer IMO. Given the large number of reports, a random corruption of index files is most probably not the case.

I found a similar issue at https://issues.apache.org/jira/browse/LUCENE-2666 which is for a newer lucene version, but the comments section mentioned that the way of using lucene can be wrong in that particular case.

In trunk, both lucene and nexus indexer changed recently. Lucene was upgraded from 2.4.1 to 2.9.3, and nexus indexer from 2.0.0 to 3.0.2.

Closing worksforme now and let's see if new reports appear with daily (or 7.0) builds.