[
https://issues.apache.org/jira/browse/LUCENE-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12837892#action_12837892
]
Michael McCandless commented on LUCENE-2280:
--------------------------------------------
Indeed that JAR is identical to 2.3.2. Weird. Not sure why the line number
doesn't line up. Irks me.
bq. Here index corruption I mean that the main index file is getting deleted
and search is not returning expected result. Hence there is no index file
exists after the NullPointerExcepton, I cannot run CheckIndex.
That's even stranger -- nothing should get deleted because a merge fails. Is
it possible your app has an exception handler doing this? Or maybe this is a
brand new index, and it doesn't get properly closed (ie, no commit) when this
exception is hit? If not... can you provide more details? An exception like
this should have no impact on the original index.
Please post the infoStream output when you get it, and report back whether this
happens on Sun's JVM. But I still can't see how either of the arrays could be
null here... this is a weird one.
Are you using the latest updates to the IBM 1.6 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
> Attachments: lucene.jar
>
>
> 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
