In this case someone outside SOLR is improperly dealing with
java.lang.VirtualMachineError in a thread outside of 'servlet'-pool.
It could be: JVM, Tomcat (dispatcher thread etc.), Lucene, STAX,
Jakarta Commons.
(of course not-stable hardware could also be a problem).
In some cases 'servlet'-thread-pool is still alive and Tomcat is not
listening on port, which clearly ;))) (I am crying...) shows that
Apache Tomcat developers do not follow Servlet and HTTP specs and
forgot to catch Error and to output 500 instead.
-Fuad
Quoting Yonik Seeley <[EMAIL PROTECTED]>:
On Tue, Sep 16, 2008 at 2:43 PM, Fuad Efendi <[EMAIL PROTECTED]> wrote:
SOLR catches everything and tries to
output (sometimes with great success) HTTP 500 with XML-formatted stacktrace
as content.
Right, as well as logging the exception.
But, it's never foolproof because the OOM exception could happen in a
non Solr thread... and in that case the behavior is completely out of
our hands.
-Yonik
