Avoiding problems using Tomcat at high-load indexes

Author Message

Jens Görisch

Wednesday 22 July 2009 10:24:25 am

Hello,

as the title may already suggest, I'm interested in using eZ Find (i.e. Solr) with a Tomcat servlet container.

The reason for this are problems, when running the default setting (with Jetty).

We have an index with overall more than 100k documents. After some time running, the Solr server runs into troubles. It doesn't update the index anymore (apparently COMMIT doesn't work) and a look into the log files reveals, that logging was stopped abruptly (i.e. the last log entry is incomplete). Also some compiled servlets are missing (e.g. <i>/solr/admin/registry.jsp</i>) and an exception is thrown, when the respective page is accessed.

All this sounds for me like it is caused by the container. Now I'm very curious, if perhaps this happened to anyone else and thus about your experiences with such kind of behaviour. Also I would like to know, if you could make improvements by using tomcat (or perhaps another servlet container).

Thanks in advance

Jens Görisch

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.