Hi, If the other suggestions for checking RAM don't help, please remove all JVM parameters from command line like the special GC configuration:
jvm_args: -Djava.util.logging.config.file=/var/lib/tomcat6/conf/logging.properties -Djava.awt.headless=true -Xms4000M -Xmx4000M -XX:PermSize=400m -XX:MaxPermSize=400m -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.endorsed.dirs=/usr/share/tomcat6/endorsed -Dcatalina.base=/var/lib/tomcat6 -Dcatalina.home=/usr/share/tomcat6 -Djava.io.tmpdir=/tmp/tomcat6-tmp The first thing I looked at was if you have aggressive optimizations enabled, but that's not the case, so you are fine :-) Uwe ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: [email protected] > -----Original Message----- > From: Dragan Jotanovic [mailto:[email protected]] > Sent: Thursday, September 01, 2011 11:13 AM > To: [email protected] > Subject: Lucene killing JVM > > Hi, > I recently upgraded to lucene 3.3 (from 3.0.3) and now my JVM keeps crashing. > I noticed that it happens when I'm closing and reopening my index. It doesn't > 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: > http://pastebin.com/wmQy0rw8 > http://pastebin.com/TYQmyHAP > > Did anyone else experience something similar? Is this a known bug in Lucene or > a JVM bug? > > Dragan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
