Re: How to get a stack trace

Chris Hostetter wrote: : I'm a new user of solr but I have worked a bit with Lucene before. I get : some out of memory exception when optimizing the index through Solr and : I would like to find out why. However, the only message I get on : standard output is: Jul 30, 2009 9:20:22 PM : org.apa

Re: How to get a stack trace

: I'm a new user of solr but I have worked a bit with Lucene before. I get : some out of memory exception when optimizing the index through Solr and : I would like to find out why. However, the only message I get on : standard output is: Jul 30, 2009 9:20:22 PM : org.apache.solr.common.SolrExc

RE: How to get a stack trace

~ David Smiley From: Nicolae Mihalache [xproma...@gmail.com] Sent: Monday, August 03, 2009 5:21 AM To: solr-user@lucene.apache.org Subject: Re: How to get a stack trace Thanks, I will try maybe together with the -XX:OnOutOfMemoryError="; ": http://java.sun.com/javase/technologies/

Re: How to get a stack trace

Thanks, I will try maybe together with the -XX:OnOutOfMemoryError="; ": http://java.sun.com/javase/technologies/hotspot/vmoptions.jsp But now I know where the problem came from, so maybe next time. On Mon, Aug 3, 2009 at 11:08 AM, Chantal Ackermann < chantal.ackerm...@btelligent.de> wrote: > ki

Re: How to get a stack trace

kill -3 [JVM-process-id] (SIGQUIT) sends a signal to the JVM to dump all thread stacks. It does NOT kill it. It's only for outputting the stacks. You can see whether there are any threads that lock up. This produces a LOT of output in the main logfile (e.g. catalina.out for Tomcat). (see for

Re: How to get a stack trace

Hello, Thanks for your answers and suggestions. I can get a heap dump also with the jmap command. The resulting file is so big that jhat gets out of memory errors itself when reading the dump. I traced back my problem (using the heap dump analyser from yourkit.com) to the FieldCache. In fact it h

Re: How to get a stack trace

Your heap may be just too small or you may have a memory leak. A stack trace may not help you since the thread encountered the OutOfMemoryError may not be where the memory leak is. A heap dump will tell you what's using up all the memory in your heap. Bill On Thu, Jul 30, 2009 at 3:54 PM, Nicola

Re: How to get a stack trace

Nicolae, You may be able to figure things out from the heap dump. You'll need to start the JVM like this, for example: java -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp/heap ... Otis -- Sematext is hiring -- http://sematext.com/about/jobs.html?mls Lucene, Solr, Nutch, Katta, Hado