It is using the default size allocated by the OS, which I don't have any
idea how much exactly. But when I use the -Xmx1024m and run this is not
occuring. Also I make some change in that loop now keeping only the Document
hitDoc = hits.doc(i); line and thats where it starts throwing error. But I
That certainly seems odd. How much memory are you allocating
your JVM?
Erick
On 4/11/07, Lokeya <[EMAIL PROTECTED]> wrote:
I have gone through the mailing list in search of posts for this error.
Though there are many, I feel my problem is little different from that and
like to get some advice
Sorry about the previous stack trace -- that was a wild goose-chase.
Here is the real culprit:
at
org.apache.lucene.index.SegmentTermEnum.growBuffer(SegmentTermEnum.java(Compiled
Code))
at
org.apache.lucene.index.SegmentTermEnum.readTerm(SegmentTermEnum.java(Compiled
Code))
at
org.apache.lucen
]
Sent: 18 August 2005 19:09
To: java-user@lucene.apache.org
Subject: Re: OutOfMemory error when searching
Fredrik wrote:
Opening the index with Luke, I can see the following:
Number of fields: 17
Number of documents: 1165726
Number of terms: 6721726
The size of the index is approx 5,3 GB.
Lucene
the IndexSearcher in this situation?
Peter
-Original Message-
From: Doug Cutting [mailto:[EMAIL PROTECTED]
Sent: 18 August 2005 19:09
To: java-user@lucene.apache.org
Subject: Re: OutOfMemory error when searching
Fredrik wrote:
> Opening the index with Luke, I can see the follow
Fredrik wrote:
Opening the index with Luke, I can see the following:
Number of fields: 17
Number of documents: 1165726
Number of terms: 6721726
The size of the index is approx 5,3 GB.
Lucene version is 1.4.3.
The index contains Norwegian terms, but lots of inline HTML, etc
is probably increasin
Yes, you need to use a single searcher instead of creating one each time.
Tony Schwartz
[EMAIL PROTECTED]
"We're going to need a lot more cowbell."
-Original Message-
From: MariLuz Elola [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 06, 2005 1:26 PM
To: java-user@lucene.apache.org
Subj
