or are we really? I think we are on 1.6 update 14 right?? sorry Im lost right now on jdk version numbering
On Thu, Nov 26, 2009 at 12:01 PM, jm <jmugur...@gmail.com> wrote: > on second thought...I hadnt noticed the jdk numbers properly, we are > using using b28, and JDK 6 Update 10 (b28) is the one fixing this... > > ok forget this then > thanks! > > On Thu, Nov 26, 2009 at 11:55 AM, jm <jmugur...@gmail.com> wrote: >> Hi, >> >> Dont know if this should be here or in java-dev, posting to this one >> first. In one of our installations, we have encountered an exception: >> >> Exception in thread "Lucene Merge Thread #0" >> org.apache.lucene.index.MergePolicy$MergeException: >> org.apache.lucene.index.CorruptIndexException: docs out of order >> (24658 <= 24658 ) >> at >> org.apache.lucene.index.ConcurrentMergeScheduler.handleMergeException(ConcurrentMergeScheduler.java:309) >> at >> org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:286) >> Caused by: org.apache.lucene.index.CorruptIndexException: docs out of >> order (24658 <= 24658 ) >> at >> org.apache.lucene.index.SegmentMerger.appendPostings(SegmentMerger.java:641) >> at >> org.apache.lucene.index.SegmentMerger.mergeTermInfo(SegmentMerger.java:586) >> at >> org.apache.lucene.index.SegmentMerger.mergeTermInfos(SegmentMerger.java:547) >> at >> org.apache.lucene.index.SegmentMerger.mergeTerms(SegmentMerger.java:500) >> at org.apache.lucene.index.SegmentMerger.merge(SegmentMerger.java:140) >> at >> org.apache.lucene.index.IndexWriter.mergeMiddle(IndexWriter.java:4231) >> at org.apache.lucene.index.IndexWriter.merge(IndexWriter.java:3884) >> at >> org.apache.lucene.index.ConcurrentMergeScheduler.doMerge(ConcurrentMergeScheduler.java:205) >> at >> org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(ConcurrentMergeScheduler.java:260) >> >> I have investigated in the list and it looked like >> https://issues.apache.org/jira/browse/LUCENE-1282. But we are using >> 2.4.1, and >> C:\Documents and Settings\Administrator>java -version >> java version "1.6.0_14" >> Java(TM) SE Runtime Environment (build 1.6.0_14-b08) >> Java HotSpot(TM) Client VM (build 14.0-b16, mixed mode) >> >> java process launched like this: >> java -server -Xmx1536m ... >> >> So I understand this bug should not be happening?? >> >> any idea? >> thanks >> javi >> > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
