Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 9150 invoked from network); 5 Apr 2011 09:25:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 5 Apr 2011 09:25:57 -0000 Received: (qmail 64370 invoked by uid 500); 5 Apr 2011 09:25:54 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 63679 invoked by uid 500); 5 Apr 2011 09:25:47 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 63670 invoked by uid 99); 5 Apr 2011 09:25:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Apr 2011 09:25:46 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of aw@ice-sa.com designates 212.85.38.228 as permitted sender) Received: from [212.85.38.228] (HELO tor.combios.es) (212.85.38.228) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Apr 2011 09:25:37 +0000 Received: from [192.168.245.129] (p549E8A9B.dip0.t-ipconnect.de [84.158.138.155]) by tor.combios.es (Postfix) with ESMTPA id CA2F42260C1 for ; Tue, 5 Apr 2011 11:25:15 +0200 (CEST) Message-ID: <4D9ADFF8.4020409@ice-sa.com> Date: Tue, 05 Apr 2011 11:25:12 +0200 From: =?ISO-8859-1?Q?Andr=E9_Warnier?= Reply-To: Tomcat Users List User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Tomcat Users List Subject: Re: Tomcat calling into itself References: <4D9ABD2D.40302@att.net> <4D9AD7EA.3040403@pidster.com> In-Reply-To: <4D9AD7EA.3040403@pidster.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Pid wrote: > On 4/5/11 7:56 AM, Michael McCutcheon wrote: >> Hello, >> >> I have a java webapp that is going to make calls to Solr. Both the >> webapp and Solr will be on the same server. > > OK. Note it's a good idea to tell us what exact OS, Java, Tomcat > versions you're running. > > >> I have heard that it is not recommended to run the webapp on the same >> tomcat instance as Solr, due to potential threading issues of tomcat >> calling into itself. > > Oh dear. That's a quite vague description, so it's really impossible to > say what it means. Can you elaborate? > > >> Would it be best to run 2 instances of tomcat (1 for webapp, another for >> Solr)? > > NEEDINFO > > >> Or is there a way to configure tomcat so that the webapp and solr can >> run in the same tomcat instance, reliably and without threading or >> performance issues? > > No idea. If Solr has threading issues (I've not heard of any) you'd > best ask that community. Tomcat is not an OS or JVM, it doesn't manage > all the threads in your app. > > Right. Plus, it is not really possible to answer these questions here, considering how many different types of configurations are possible with Solr and Lucene. The OP really needs to ask on the Solr/Lucene lists, for what would be the most appropriate configuration for *his* use case. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org