Netflix uses Tomcat throuought and they tail the log to figure out whether it has started, except they look for a message from Solr to see whether Solr is ready to go to work.
wunder -----Original Message----- From: Lajos [mailto:la...@protulae.com] Sent: Friday, October 02, 2009 1:35 PM To: solr-user@lucene.apache.org Subject: Re: Advantages of different Servlet Containers Just go for Tomcat. For all its problems, and I should know having used it since it was originally JavaWebServer, it is perfectly capable of handling high-end production environments provided you tune it correctly. We use it with our customized Solr 1.3 version without any problems. Lajos Simon Wistow wrote: > I know that the Solr FAQ says > > "Users should decide for themselves which Servlet Container they > consider the easiest/best for their use cases based on their > needs/experience. For high traffic scenarios, investing time for tuning > the servlet container can often make a big difference." > > but is there anywhere that lists some of the variosu advantages and > disadvantages of, say, Tomcat over Jetty for someone who isn't current > with the Java ecosystem? > > Also, I'm currently using Jetty but I've had to do a horrific hack to > make it work under init.d in that I start it up in the background and > then tail the output waiting for the line that says the SocketConnector > has been started > > while [ '' = "$(tail -1 $LOG | grep 'Started SocketConnector')" ] ; > do > sleep 1 > done > > There's *got* to be a better way of doing this, right? > > Thanks, > > Simon > > > > ------------------------------------------------------------------------ > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.5.409 / Virus Database: 270.14.2/2408 - Release Date: 10/01/09 18:23:00 >
