I much prefer "jstack" (which comes with the JDK) which is for exactly this purpose. I always forget the right number for using kill. When using jstack, the stack goes to the current terminal session, not Solr's output -- very convenient.
~ 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="<cmd args>; <cmd args>": 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: > 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 example > > http://www.unixville.com/~moazam/stories/2004/05/18/debuggingHangsInTheJvm.html<http://www.unixville.com/%7Emoazam/stories/2004/05/18/debuggingHangsInTheJvm.html> > and others) > > > Otis Gospodnetic schrieb: > >> 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, Hadoop, HBase, UIMA, NLP, NER, IR >> >> >> >> ----- Original Message ---- >> >>> From: Nicolae Mihalache <xproma...@yahoo.com> >>> To: solr-user@lucene.apache.org >>> Sent: Thursday, July 30, 2009 3:54:41 PM >>> Subject: How to get a stack trace >>> >>> Hello, >>> >>> 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.SolrException log >>> SEVERE: java.lang.OutOfMemoryError: Java heap space >>> >>> Is there a way to get a stack trace for this exception? I had a look into >>> the >>> java.util.logging options and didn't find anything. >>> >>> My solr runs in some standard configuration inside jetty. >>> Any suggestion would be appreciated. >>> >>> Thanks, >>> nicolae >>> >> >> > -- > Chantal Ackermann > Consultant > > mobil +49 (176) 10 00 09 45 > email chantal.ackerm...@btelligent.de > > > -------------------------------------------------------------------------------------------------------- > > b.telligent GmbH & Co. KG > Lichtenbergstraße 8 > D-85748 Garching / München > > fon +49 (89) 54 84 25 60 > fax +49 (89) 54 84 25 69 > web www.btelligent.de > > Registered in Munich: HRA 84393 > Managing Director: b.telligent Verwaltungs GmbH, HRB 153164 represented by > Sebastian Amtage and Klaus Blaschek > USt.Id.-Nr. DE814054803 > > > > Confidentiality Note > This email is intended only for the use of the individual or entity to > which it is addressed, and may contain information that is privileged, > confidential and exempt from disclosure under applicable law. If the reader > of this email message is not the intended recipient, or the employee or > agent responsible for delivery of the message to the intended recipient, you > are hereby notified that any dissemination, distribution or copying of this > communication is prohibited. If you have received this email in error, > please notify us immediately by telephone at +49 (0) 89 54 84 25 60. Thank > you. >
