Thanks Uwe and Simon and for your detailed answers.
I'm reviewing my code to find where I'm using a closed index.
Roberto
On Nov 22, 2011, at 11:53 AM, Uwe Schindler wrote:
> Hi,
>
> The JDK issues you are talking about are also fixed in 1.6.9_29 (not only
> 1.7.0u1). So your crash is not rel
Hi,
The JDK issues you are talking about are also fixed in 1.6.9_29 (not only
1.7.0u1). So your crash is not related to any of the "famous java6/7 bugs"
(in addition, the vint bug does *not* crash your JVM at all it just corrupts
your index by returning wrong values - and this one is definitely fi
hey,
are you using mmap directory by any chance? Stuff like this often
happens when you try to read from a already closed mmaped file.
Typically you try to search or read from a already closed
IndexSearcher / IndexReader, is it possible that you use a stale
IndexReader in a in-flight search? The u
It may well be to do with this Hotspot bug:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6407471
Note, the bug only appears when you invoke java with the "-server"
command line option.
Kieran
Dan Armbrust wrote:
Ross Rankin wrote:
We keep getting JVM crashes on 1.4.3. I found in t
Ross Rankin wrote:
We keep getting JVM crashes on 1.4.3. I found in the archive that setting a
JVM parameter solved the problem for a few users. We've tried that and it
has not worked. Here's our JVM parameters:
Why not try a new JVM?
Either a newer sun... or a JDK, or a blackdown...
In o
Java apps shouldn't throw these kind of seg faults.
Sounds like a problem with memory. Especially if you can't
reproduce the error in the same location. Double especially
if you have the same problems elsewhere under heavy
memory load. I had all kinds of problems with seg faults
in the JVM unt
We had a similar problem. We discovered that it was basically that eden/from
was out of memory and made two changes and that seems to have helped:
1. Reduce [Max]PermSize to 128M
2. Use the concurrent garbage collector
Good luck.
-h
--- Ross Rankin <[EMAIL PROTECTED]> wrote:
> We keep gettin
@lucene.apache.org
Subject: Re: JVM Crash in Lucene
Got the same problem. Running 1.5.0_05 on Solaris 10. I've seen that
this issue has been reported on Sun's forum but no answer yet.
Another interesting thing which I noticed. We previously used the
RAMDirectory and we never got JVM-crashes
Got the same problem. Running 1.5.0_05 on Solaris 10. I've seen that
this issue has been reported on Sun's forum but no answer yet.
Another interesting thing which I noticed. We previously used the
RAMDirectory and we never got JVM-crashes when using RAMDirectory.
However, once we started using FS
You also might try -Xbatch or -Xcomp to see if that fixes it (or
reproduces it faster).
Here's a great list of JVM options:
http://blogs.sun.com/roller/resources/watt/jvm-options-list.html
-Yonik
On 12/11/05, Yonik Seeley <[EMAIL PROTECTED]> wrote:
> Sounds like it's a hotspot bug.
> AFAIK, hots
Sounds like it's a hotspot bug.
AFAIK, hotspot doesn't just compile a method once... it can do
optimization over time.
To work around it, have you tried pre previous version: 1.5_05?
It's possible it's a fairly new bug. We've been running with that
version and Lucene 1.4.3 without problems (on Op
First, thank you Chris, Yonik, and Dan for your ideas as to what might be
causing this problem.
I tried moving things around so that the IndexReader is still open when it
calls TermFreqVector.getTerms()/TermFreqVector.getTermFrequencies(). It
didn't seem to make any difference.
I also tried
MaxPermSize is a not-always-documented jvm flag similar to Xmx. You set it like
this...
java -Xmx200M -XX:MaxPermSize=100m Myclass
It sets the maximum amount of space that will be available to the jvm for
'permanent' things (classes, etc.) and defaults to just 64MB. This can often
run out wit
The only problems I've had with 1.5 JVM crashes and Lucene was related
to stack overflow... try increasing the stack size and see of anything
different happens.
My crashes happened while trying to use Luke to open a 4GB index with
thousands of indexed fields.
-Yonik
-
: I'm relatively new to Lucene. When I run my app, I get a JVM error.
: This gets called a lot, but only fails every once in awhile (maybe 1 in
: 100 calls?)
i'm not that familiar with TermFreqVectors, and I have no idea what
indexManager is, but I'm suprised this works at all ... I thought calli
15 matches
Mail list logo
