Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <4BC97A7E.3020208@atcult.it>
Date: Sat, 17 Apr 2010 11:08:14 +0200
From: Andrea Gazzarini <andrea.gazzarini@atcult.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; it;
 rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: solr-user@lucene.apache.org
Subject: Jetty, Tomcat or JBoss?
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit

Hi all,
I have a web application which is basically a (user) search interface 
towards SOLR.
My index is something like 7GB and has a lot of records so apart other 
things like optiming SOLR schema, config ,clustering etc... I'd like to 
keep SOLR installation as light as possible.
At the moment my SOLR instance is running under JBoss but I saw that 
running under the bundled Jetty it takes a very little amount of memory 
(at least at startup and after one hour of usage)

So my questions is: since SOLR is using JEE web components what are the 
drawback of using the following architecture?

-My Application (Full JEE application with web components and EJB) on JBoss;
- SOLR on Jetty or Tomcat

Having said that and supposing that the idea is good, what are the main 
differences / advantages / disadvamtages (from this point of view) 
between Tomcat and Jetty?

Best Regards,
Andrea