closed indexes.
>
> Uwe
>
> -
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: u...@thetaphi.de
>
>
>> -Original Message-----
>> From: Roberto Fonti [mailto:roberto.fo...@gmail.com]
>> Sent: Tuesday, Nove
r-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Roberto Fonti [mailto:roberto.fo...@gmail.com]
> Sent: Tuesday, November 22, 2011 8:03 PM
> To: java-user@lucene.apache.org
> Subject: JVM Crash org.apache.lucene.store.Data
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
My JVM (1.6.0_29) keeps crashing on intensive use when indexing documents with
Lucene. I get:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x2b6b196d767c, pid=26417, tid=1183217984
#
# JRE version: 6.0_29-b11
# Java VM: Java HotSpot(TM) 64-Bit
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
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:
-Xms512m -Xmx1024m -XX:PermSize=256m
We're running Tomcat 5.5.16. Any Idea?
If it's an
@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
um.com/gcviewer-vmflags.html
http://java.sun.com/docs/hotspot/gc/
http://www.unixville.com/~moazam/stories/2004/05/17/maxpermsizeAndHowItRelatesToTheOverallHeap.html
hth
Dan
-Original Message-
From: Dan Gould [mailto:[EMAIL PROTECTED]
Sent: 09 December 2005 01:49
To: java-user@lucene.apache.org
Sub
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
-
ng
for to go bye-bye because you closed the reader?
(it sounds silly when I read it back to myself ... but it's the best guess
i've got just reading your code)
: My code that is causing the JVM crash is:
:
: //Get the terms and frequencies
: IndexReader indexreader = n
.so+0x25f3c7]
V [libjvm.so+0x2bed06]
V [libjvm.so+0x2be6b2]
V [libjvm.so+0x6163f9]
V [libjvm.so+0x610ffe]
V [libjvm.so+0x554745]
Current CompileTask:
opto:1621
org.apache.lucene.index.IndexReader$1.doBody()Ljava/lang/Object;
(99 bytes)
My code that is causing the JVM crash is:
//Ge
18 matches
Mail list logo
