Return-Path: X-Original-To: apmail-lucene-java-user-archive@www.apache.org Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BE95C8385 for ; Thu, 1 Sep 2011 10:51:01 +0000 (UTC) Received: (qmail 261 invoked by uid 500); 1 Sep 2011 10:50:57 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 99553 invoked by uid 500); 1 Sep 2011 10:50:42 -0000 Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-user@lucene.apache.org Delivered-To: mailing list java-user@lucene.apache.org Received: (qmail 99504 invoked by uid 99); 1 Sep 2011 10:50:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Sep 2011 10:50:38 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of uwe@thetaphi.de designates 188.138.97.18 as permitted sender) Received: from [188.138.97.18] (HELO mail.sd-datasolutions.de) (188.138.97.18) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Sep 2011 10:50:32 +0000 Received: from VEGA (gate2.marum.de [134.102.237.2]) by mail.sd-datasolutions.de (Postfix) with ESMTPSA id BE84114AA0F0 for ; Thu, 1 Sep 2011 10:50:10 +0000 (UTC) From: "Uwe Schindler" To: References: <4E5F4C88.9050007@diosphere.com> In-Reply-To: <4E5F4C88.9050007@diosphere.com> Subject: RE: Lucene killing JVM Date: Thu, 1 Sep 2011 12:51:12 +0200 Message-ID: <006601cc6895$11203140$336093c0$@thetaphi.de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQF2iIK8N3qlQCe9VYLDK/F3/ImacZXkGJmg Content-Language: de 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: uwe@thetaphi.de > -----Original Message----- > From: Dragan Jotanovic [mailto:dragan.jotanovic@diosphere.com] > Sent: Thursday, September 01, 2011 11:13 AM > To: java-user@lucene.apache.org > 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: java-user-unsubscribe@lucene.apache.org > For additional commands, e-mail: java-user-help@lucene.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org