Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 51415 invoked from network); 16 Oct 2009 10:14:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 16 Oct 2009 10:14:01 -0000 Received: (qmail 65812 invoked by uid 500); 16 Oct 2009 10:13:57 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 65747 invoked by uid 500); 16 Oct 2009 10:13:57 -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 65736 invoked by uid 99); 16 Oct 2009 10:13:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Oct 2009 10:13:57 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of knst.kolinko@gmail.com designates 209.85.220.225 as permitted sender) Received: from [209.85.220.225] (HELO mail-fx0-f225.google.com) (209.85.220.225) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Oct 2009 10:13:49 +0000 Received: by fxm25 with SMTP id 25so2313110fxm.0 for ; Fri, 16 Oct 2009 03:13:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=vE7Bf6geAoIiBD88tCP5EcosEYqRWmaoQxSUZzgESRg=; b=G6lIR/l01eZ+QhveFxIvCIOKYZ1nMxWW6jOYmr7jCyiSIGMjTExlk7wnZkpoELsoka Hp7lFIndYpYy3ep51Mbn3XT6eIaHgc8KaRBv5Ekc302os/yWxRRjXeS3V29egZIzCxmZ qy9q/+awQ3Zs5kX4NHLcfjeftKlodD+jVdstI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=BmjsZbnxjApPy+eiVH/nma4VpILxhcDS9UzyEy7DDSORAqQuyn4fnKu84iTJt/D8wh arMDwia4kmTCXZHfNE9HjgV6RX/K3bIYyOPyNsRUbxQFlGwI52Sc3IJlDoQ/JKK27w+5 vu0QjgdHJNpLsw1vWALRJ/EKZy7suXDO8RBo4= MIME-Version: 1.0 Received: by 10.103.76.21 with SMTP id d21mr530907mul.78.1255688009145; Fri, 16 Oct 2009 03:13:29 -0700 (PDT) In-Reply-To: <7dc70cc60910151025g3041ccacr7a0c77f6e4fb0990@mail.gmail.com> References: <7dc70cc60910151025g3041ccacr7a0c77f6e4fb0990@mail.gmail.com> Date: Fri, 16 Oct 2009 14:13:28 +0400 Message-ID: <427155180910160313p6d678051wf778eb5bc4a8f924@mail.gmail.com> Subject: Re: catalina - when to use "start" and "run" From: Konstantin Kolinko To: Tomcat Users List Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org 2009/10/15 Anand HS : > using "start" spawned the server start up in a new console where as "run" > started in the same console. > > Other than this is there any obvious difference in using one or the other. ? > That has to be the only difference. "catalina start" command is what is written in startup.(sh|bat) There are cases, when configuration is broken, so that Tomcat cannot start. In that case it might be that the secondary console window will close immediately, and the user won't be able to see the error message that was printed there. If that occurs, our first advice is to try "catalina run" so to be able to see the error message. That is why the option is there, I think. By the way, it is not necessary to use catalina.(bat|sh) at all. The command line that starts java using bootstrap.jar is that what matters in the end. I think you can figure the rest by yourself. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org