I've seen plenty of OOMs logged :) But you can run things like jconsole or jmap (with -heap or -histo or -histo:live options) to see how the JVM is doing with memory.
Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch ----- Original Message ---- > From: Peter Williams <[EMAIL PROTECTED]> > To: solr-user@lucene.apache.org > Sent: Tuesday, September 16, 2008 11:17:11 AM > Subject: Re: Solr stops listening > > Thanks. > > Does a message about what went wrong not get written to the log because by > the OOME happens there is not enough memory to actually construct the > message? > > Peter > > On Mon, Sep 15, 2008 at 2:40 PM, Fuad Efendi wrote: > > > > > SOLR main servlet catches all Throwable. In case of very popular OOME with > > standard JVM from SUN you will get exactly this behaviour. > > ============== > > http://www.tokenizer.org/bot.html > > > > > > > > Quoting Peter Williams : > > > > I am using Solr 1.2.0 with Jetty and I am experiencing some odd failures > >> of > >> Solr. Solr seems to just stops listening for new TCP connections. The > >> Solr > >> process continues running and log contains nothing suspicious (to me, > >> anyway) but curl requests against the server fail with "connection > >> refused" > >> and `netstat --listening` does not list the Solr port. Restarting Solr > >> fixes the problem (curl request work, etc). This happens once or more a > >> day. > >> > >> Any one have any ideas about how to figure out what is going wrong? > >> > >> Peter Williams > >> > >> > > > > > >
