[
https://issues.apache.org/jira/browse/LUCENE-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12837204#action_12837204
]
Michael McCandless commented on LUCENE-2280:
--------------------------------------------
Are you sure you're using a stock version 2.3.2 of Lucene?
I ask because... the line numbers in SegmentMerger (specifically 566) don't
correlate to 2.3.2. The other line numbers do match. It's odd.
But looking at the code I don't see how either of the arrays being passed to
System.arraycopy can be null.
Can you turn on IndexWriter's infoStream and capture & post the output?
It's also strange that this leads to index corruption; it shouldn't (the merge
should just fail, and the index should be untouched). Can you run CheckIndex
on the index and post what corruption it uncovers.
Does this happen in a Sun JRE?
> IndexWriter.optimize() throws NullPointerException
> --------------------------------------------------
>
> Key: LUCENE-2280
> URL: https://issues.apache.org/jira/browse/LUCENE-2280
> Project: Lucene - Java
> Issue Type: Bug
> Components: Index
> Affects Versions: 2.3.2
> Environment: Win 2003, lucene version 2.3.2, IBM JRE 1.6
> Reporter: Ritesh Nigam
>
> I am using lucene 2.3.2 search APIs for my application, i am indexing 45GB
> database which creates approax 200MB index file, after finishing the indexing
> and while running optimize() i can see NullPointerExcception thrown in my log
> and index file is getting corrupted, log says
> ------------------------------------------------------------------------
> Caused by:
> java.lang.NullPointerException
> at
> org.apache.lucene.store.BufferedIndexOutput.writeBytes(BufferedIndexOutput.java:49)
> at org.apache.lucene.store.IndexOutput.writeBytes(IndexOutput.java:40)
> at
> org.apache.lucene.index.SegmentMerger.mergeNorms(SegmentMerger.java:566)
> at org.apache.lucene.index.SegmentMerger.merge(SegmentMerger.java:135)
> at
> org.apache.lucene.index.IndexWriter.mergeMiddle(IndexWriter.java:3273)
> at org.apache.lucene.index.IndexWriter.merge(IndexWriter.java:2968)
> at
> org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:240)
> ------------------------------------------------------------------------
> and this is happening quite frequently, although I am not able to reproduce
> it on demand, I saw an issue logged which is some what related to mine issue
> (http://mail-archives.apache.org/mod_mbox/lucene-solr-user/200809.mbox/%3c6e4a40db-5efc-42da-a857-d59f4ec34...@mikemccandless.com%3e)
> but the only difference here is I am not using Store.Compress for my fields,
> i am using Store.NO instead. please note that I am using IBM JRE for my
> application.
> Is this an issue with lucene?, if yes it is fixed in which version?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
