Toke Eskildsen wrote:
On Wed, 2010-02-17 at 15:18 +0100, Michael van Rooyen wrote:
I recently upgraded from version 2.3.2 to 2.9.1. [...]
Since going live a few days ago, however, we've twice had read past
EOF exceptions.
The first thing to do is check the Java version. If you're using Sun
Toke Eskildsen wrote:
On Wed, 2010-02-17 at 15:18 +0100, Michael van Rooyen wrote:
I recently upgraded from version 2.3.2 to 2.9.1. [...]
Since going live a few days ago, however, we've twice had read past EOF
exceptions.
The first thing to do is check the Java version. If you're usin
On Wed, 2010-02-17 at 15:18 +0100, Michael van Rooyen wrote:
> I recently upgraded from version 2.3.2 to 2.9.1. [...]
> Since going live a few days ago, however, we've twice had read past EOF
> exceptions.
The first thing to do is check the Java version. If you're using Sun JRE
1.6.0, you might h
what we could
do to avoid it happening? The stack trace for the EOF exception is below.
Thanks,
Michael.
Caused by: java.io.IOException: read past EOF
org.apache.lucene.index.CompoundFileReader$CSIndexInput.readInternal(CompoundFileReader.java:245)
org.apache.lucene.store.Buffe
Ok. Just to followup, I performed the same steps with another of our indexes
and did not have the same issue:
Opening index @ /lucenedata/index4
Segments file=segments_85 numSegments=1 version=FORMAT_HAS_PROX [Lucene 2.4]
1 of 1: name=_42 docCount=3986767
compound=true
hasProx=true
Hi:
Could you try open the index using Luke but using the JDK bundled
with the Oracle DB?
I mean, try to use Luke as an standalone application in the same
machine but outside the OJVM using the JDK at:
$ORACLE_HOME/jdk
which was used to compile most of the classes running inside the OJV
Michael McCandless-2 wrote:
>
> That exception seems to indicate that the fdx file being opened by
> FieldsReader is 0 length (it's trying to read the first int from that
> file).
>
> Is the exception repeatable, if you try again to call
> IndexReader.open?
>
> It's odd that CheckIndex finds
Toke Eskildsen wrote:
>
> A quick check when a corrupt index problem is encountered:
> Does any of your machines run Java 1.6.0_04-1.6.0_10b25?
>
Thanks Toke.
As I mentioned in my response to Erick, this is complicated by the fact that
the error is within a java stored procedure in Oracle. Th
Erick Erickson wrote:
>
> I guess my first question, based on your statement that you ran
> checkindex from a different machine would be whether you have
> the same version of Lucene installed on both machines? And how
> did you get your index where it is now? did you optmize it in place
> or d
to open
the index I get this:
java.io.IOException: read past EOF
at
org
.apache
.lucene.store.BufferedIndexInput.readBytes(BufferedIndexInput.java)
at
org.apache.lucene.index.CompoundFileReader
$CSIndexInput.readInternal(CompoundFileReader.java)
On Tue, 2009-01-06 at 23:07 +0100, 1world1love wrote:
> Greetings all. I have an index that I have optimized and when I try to open
> the index I get this:
>
> java.io.IOException: read past EOF
A quick check when a corrupt index problem is encountered:
Does any of your machi
open
> the index I get this:
>
> java.io.IOException: read past EOF
>at
>
> org.apache.lucene.store.BufferedIndexInput.readBytes(BufferedIndexInput.java)
>at
>
> org.apache.lucene.index.CompoundFileReader$CSIndexInput.readInterna
Greetings all. I have an index that I have optimized and when I try to open
the index I get this:
java.io.IOException: read past EOF
at
org.apache.lucene.store.BufferedIndexInput.readBytes(BufferedIndexInput.java)
at
org.apache.lucene.index.CompoundFileReader
>>>> 22 _0.fnm
>>>> 48 _0.fdt
>>>> 20 _0.fdx
>>>> 62 segments_2
>>>> I'll add some debugging information at my classes which save/load
>>>> buffers t
hread]: DW: apply 2 buffered deleted terms and 0
deleted
docIDs and 0 deleted queries on 3 segments.
IW 3 [Root Thread]: hit exception flushing deletes
Exception in thread "Root Thread" java.io.IOException: read past
EOF
at
org
.apache
.lucene.store.BufferedIndexInput.refill(BufferedIndexInput
new index?
>>>
>>> We did change the index format in 2.4 to use "true" UTF8 encoding for all
>>> text content; not sure that this applies here (to BufferedIndexReader
>>> it's
>>> all bytes)
| +46 765 27 19 55 | [EMAIL PROTECTED] |
www.mogul.com
> -Original Message-
> From: Marcelo Ochoa [mailto:[EMAIL PROTECTED]
> Sent: den 26 september 2008 20:54
> To: java-user@lucene.apache.org
> Subject: [SPAM] - Re: Caused by: java.io.IOException: read
> past EOF on Sl
ize=264
docs/MB=7,943.758 new/old=0.237%
IW 3 [Root Thread]: DW: apply 2 buffered deleted terms and 0 deleted
docIDs and 0 deleted queries on 3 segments.
IW 3 [Root Thread]: hit exception flushing deletes
Exception in thread "Root Thread" java.io.IOException: read past EOF
at
or
I will try the other stuff and will let you know.
This is how we do the search ,
we will get the Hits in one call and we will make another call to get the
data from lucene.
My guess is when it gets the matching Hits it getting from master and when
it tries to retrieve the actual data its hittin
rue flushDocStores=false
>> numDocs=2 numBufDelTerms=2
>> IW 3 [Root Thread]: index before flush _1:C2->_1 _2:C2->_2
>> IW 3 [Root Thread]: DW: flush postings as segment _3 numDocs=2
>> IW 3 [Root Thread]: DW: oldRAMSize=111616 newFlushedSize=264
>> doc
Which version of Lucene is this? Looks like 2.3.x -- what's the x?
Can you run your app server with assertions enabled for
org.apache.lucene.*? It may catch something sooner.
Can you try running CheckIndex after the snapshot is produced, just to
see if there is any corruption?
Your fir
Exception in thread "Root Thread" java.io.IOException: read past EOF
at
org
.apache
.lucene.store.BufferedIndexInput.refill(BufferedIndexInput.java)
at
org
.apache
.lucene.store.BufferedIndexInput.readBytes(BufferedIndexInput.java)
at
org
.apache
.lucen
ecutor
>> $Worker.run(ThreadPoolExecutor.java:907)
>>at java.lang.Thread.run(Thread.java:619)
>> Caused by: com.IndexingException: [SYSTEM_ERROR] Cannot access index
>> [data_dir/index]: [read past EOF]
>>at
>> c
gments.
IW 3 [Root Thread]: hit exception flushing deletes
Exception in thread "Root Thread" java.io.IOException: read past EOF
at
org.apache.lucene.store.BufferedIndexInput.refill(BufferedIndexInput.java)
at
org.apache.lucene.store.BufferedIndexInput.readBytes(Buffere
java.lang.Thread.run(Thread.java:619)
Caused by: com.IndexingException: [SYSTEM_ERROR] Cannot access index
[data_dir/index]: [read past EOF]
at
com
.lucene
.LuceneSearchService.getSearchResults(LuceneSearchService.java:964)
... 12 more
Caused by: java.io.IOException: read past EOF
com.lucene.LuceneSearchService.getSearchResults(LuceneSearchService.java:964)
... 12 more
Caused by: java.io.IOException: read past EOF
at
org.apache.lucene.store.BufferedIndexInput.refill(BufferedIndexInput.java:146)
at
org.apache.lucene.store.BufferedIndexInput.readByte(BufferedIndexInput.java:38)
at
turns out i needed a seek method.
i ended up modeling it after the RAM Directory.
i turned the RAMFile into an @Entity.
the directory accesses the EntityManager.
and i am using JBossCache.
preliminary testing shows comparable response times.
section
of the .cfs file.
Does anyone have any suggestions?
Thanks!
Here is more background info:
- Using version 1.4.3
- Stack trace
java.io.IOException: read past EOF
at org.apache.lucene.store.InputStream.refill(InputStream.java:154)
at org.apache.lucene.store.InputStream.readByte
John Gilbert <[EMAIL PROTECTED]> wrote on 14/10/2006 20:14:43:
> I am trying to write an Ejb3Directory. It seems to work for index
> writing but not for searching.
> I get the EOF exception. I assume this means that either my
> OutputStream or InputStream is doing
> something wrong. It fails becaus
section
of the .cfs file.
Does anyone have any suggestions?
Thanks!
Here is more background info:
- Using version 1.4.3
- Stack trace
java.io.IOException: read past EOF
at org.apache.lucene.store.InputStream.refill(InputStream.java:154)
at org.apache.lucene.store.InputStream.readByte
clues?
From: Dmitry Goldenberg [mailto:[EMAIL PROTECTED]
Sent: Tue 1/24/2006 3:52 PM
To: java-user@lucene.apache.org
Cc: java-dev@lucene.apache.org
Subject: java.io.IOException: read past EOF in BufferedIndexInput.refill
Has anyone seen this exception and been able to resolve the
Has anyone seen this exception and been able to resolve the cause? I have seen
numerous mentions of it in the Lucene lists archives but no resolutions, looks
like. Anyone? Thanks.
java.io.IOException: read past EOF
at
org.apache.lucene.store.BufferedIndexInput.refill
updates following the same steps. I'm curious as what might cause this so
I can fix any problems in my indexing code.
May-12 18:20:34 WARN !!! Unable to close Lucene index writer
java.io.IOException: read past EOF
at org.apache.lucene.store.InputStream.refill(InputStream.java:154
33 matches
Mail list logo
