lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler" <>
Subject RE: Lucene killing JVM
Date Thu, 01 Sep 2011 10:51:12 GMT

If the other suggestions for checking RAM don't help, please remove all JVM
parameters from command line like the special GC configuration:

-Djava.awt.headless=true -Xms4000M -Xmx4000M -XX:PermSize=400m
-XX:MaxPermSize=400m -XX:+UseConcMarkSweepGC -XX:+UseParNewGC
-Dcatalina.base=/var/lib/tomcat6 -Dcatalina.home=/usr/share/tomcat6

The first thing I looked at was if you have aggressive optimizations
enabled, but that's not the case, so you are fine :-)


Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen

> -----Original Message-----
> From: Dragan Jotanovic []
> Sent: Thursday, September 01, 2011 11:13 AM
> To:
> Subject: Lucene killing JVM
> Hi,
> I recently upgraded to lucene 3.3 (from 3.0.3) and now my JVM keeps
> I noticed that it happens when I'm closing and reopening my index. It
> happen every time. Sometimes it works for days and sometimes it crashes
> several times a day. Usually there is no exception in log files, only that
JVM dies
> and error report file is created.
> Index server is running on Tomcat 6, Ubuntu server 10.04, Sun JVM 1.6.0_26
> Here's two examples of error report files:
> Did anyone else experience something similar? Is this a known bug in
Lucene or
> a JVM bug?
> Dragan
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message