Return-Path: X-Original-To: apmail-lucene-solr-user-archive@minotaur.apache.org Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4647B10741 for ; Tue, 10 Feb 2015 17:06:02 +0000 (UTC) Received: (qmail 636 invoked by uid 500); 10 Feb 2015 17:05:57 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 569 invoked by uid 500); 10 Feb 2015 17:05:57 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Received: (qmail 557 invoked by uid 99); 10 Feb 2015 17:05:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Feb 2015 17:05:57 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of apache@elyograg.org designates 166.70.79.219 as permitted sender) Received: from [166.70.79.219] (HELO frodo.elyograg.org) (166.70.79.219) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Feb 2015 17:05:52 +0000 Received: from localhost (localhost [127.0.0.1]) by frodo.elyograg.org (Postfix) with ESMTP id 815D672F4 for ; Tue, 10 Feb 2015 10:05:25 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elyograg.org; h= content-transfer-encoding:content-type:content-type:in-reply-to :references:subject:subject:mime-version:user-agent:from:from :date:date:message-id:received:received; s=mail; t=1423587925; bh=iTgsnQEQNrRdNA/mPJAtzunKJGZtybqgTn/h6Sw8ynY=; b=n8EQVZOBBYUJ f8I6LfVozPZZXPNVywlpG/2l6n1ZLHXc62UoCZzyIEF2NWqc0QKM+eGYCGClh2Uw rEhDq7tc9O3HlhilZ9BZ3L+L3cRz1iTfjfkJhj4vG3SsRSft2phhENSy+JJ6gJDb e7CUp37Y84MWduvyjRE8wpGaCxaYzVY= X-Virus-Scanned: Debian amavisd-new at frodo.elyograg.org Received: from frodo.elyograg.org ([127.0.0.1]) by localhost (frodo.elyograg.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Ak1WN02dT0VI for ; Tue, 10 Feb 2015 10:05:25 -0700 (MST) Received: from [10.2.0.108] (client175.mainstreamdata.com [209.63.42.175]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: elyograg@elyograg.org) by frodo.elyograg.org (Postfix) with ESMTPSA id 2CEF472D9 for ; Tue, 10 Feb 2015 10:05:23 -0700 (MST) Message-ID: <54DA3A49.1090604@elyograg.org> Date: Tue, 10 Feb 2015 10:05:13 -0700 From: Shawn Heisey User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: solr-user@lucene.apache.org Subject: Re: Solr on Tomcat References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 2/10/2015 9:48 AM, Matt Kuiper wrote: > I am starting to look in to Solr 5.0. I have been running Solr 4.* on Tomcat. I was surprised to find the following notice on https://cwiki.apache.org/confluence/display/solr/Running+Solr+on+Tomcat (Marked as Unreleased) > > Beginning with Solr 5.0, Support for deploying Solr as a WAR in servlet containers like Tomcat is no longer supported. > > I want to verify that it is true that Solr 5.0 will not be able to run on Tomcat, and confirm that the recommended way to deploy Solr 5.0 is as a Linux service. Solr will eventually (hopefully soon) be entirely its own application. The documentation you have seen in the reference guide is there to prepare users for this eventuality. Right now we are in a transition period. We have built scripts for controlling the start and stop of the example server installation. Under the covers, Solr is still a web application contained in a war and the example server still runs an unmodified copy of jetty. Down the road, when Solr will becomes a completely standalone application, we will merely have to modify the script wrapper to use it, and the user may not even notice the change. With 5.0, if you want to run in tomcat, you will be able to find the war in the download's server/webapps directory and use it just like you do now ... but we will be encouraging people to NOT do this, because eventually it will be completely unsupported. Thanks, Shawn