Return-Path: 
 <users-return-191787-apmail-tomcat-users-archive=tomcat.apache.org@tomcat.apache.org>
Delivered-To: apmail-tomcat-users-archive@www.apache.org
Received: (qmail 83915 invoked from network); 15 Feb 2009 17:33:17 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 15 Feb 2009 17:33:17 -0000
Received: (qmail 62409 invoked by uid 500); 15 Feb 2009 17:33:04 -0000
Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org
Received: (qmail 62386 invoked by uid 500); 15 Feb 2009 17:33:04 -0000
Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@tomcat.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@tomcat.apache.org>
List-Post: <mailto:users@tomcat.apache.org>
List-Id: <users.tomcat.apache.org>
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Delivered-To: mailing list users@tomcat.apache.org
Received: (qmail 62375 invoked by uid 99); 15 Feb 2009 17:33:04 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 15 Feb 2009 09:33:04 -0800
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 aw@ice-sa.com designates
 212.85.38.174 as permitted sender)
Received: from [212.85.38.174] (HELO popeye.combios.es) (212.85.38.174)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 15 Feb 2009 17:32:54 +0000
Received: from [192.168.245.129] (p549EB56F.dip0.t-ipconnect.de
 [84.158.181.111])
	(authenticated bits=0)
	by popeye.combios.es (8.13.8/8.13.8/Debian-3) with ESMTP id n1FHWXam014188
	for <users@tomcat.apache.org>; Sun, 15 Feb 2009 18:32:33 +0100
Message-ID: <4998509E.7010800@ice-sa.com>
Date: Sun, 15 Feb 2009 18:27:58 +0100
From: =?ISO-8859-1?Q?Andr=E9_Warnier?= <aw@ice-sa.com>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: Please help with setting up a tomcat configuration in
 	production...
References: <1460a1a20902150813q5e1986acqe13c8673d0c62087@mail.gmail.com>
	 <49984147.5000909@ice-sa.com>
	 <1460a1a20902150848q1697ef2cu68a7762c1b83a4e1@mail.gmail.com>
 <1460a1a20902150909leae36e2l3a8719149de5f648@mail.gmail.com>
In-Reply-To: <1460a1a20902150909leae36e2l3a8719149de5f648@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV 0.92.1/8993/Sun Feb 15 06:53:41 2009 on
 popeye.combios.es
X-Virus-Status: Clean
X-Virus-Checked: Checked by ClamAV on apache.org

Julien Martin wrote:
> 
> I now get a 404 tomcat error.
> 
> Any one could please help?
> 
We're trying.  But you are not making it easy, by making several changes 
at once and then not telling us about it until it is too late.

First, you have already modified the standard Tomcat configuration, by 
making that second Host the default one (in <Engine>).  You should 
probably not do that, or not yet.

Second, before you create a second Host with a name like 
"jeanbaptistemartin.com", is that name a real DNS name, that resolves to 
the IP address of your physical Tomcat host ?
Because if it isn't the case, then it will not work, no matter what else.

Third, you should probably *not* have a <Context> element in your 
server.xml.

Although this is explained in the on-line documentation, and has been 
explained many times before in this forum (and these previous 
explanations are available on-line, and searchable), let me give you a 
quick overview :

- the appBase attribute of your Host element tells Tomcat, /for this 
Host/, where the applications can normally be found.
By default, this is the "webapps" directory under the main Tomcat 
installation directory (or more exactly, under the CATALINA_BASE directory).
- you can change the above by creating a specific Context element for 
your webapp, but you should only do that if there is no other way 
(because it is confusing).  And if you create such a Context element, 
you should not put it in the server.xml file.  It goes somewhere else, 
which I will tell you another time.
- a webapp can consist either of the "developed" directory structure of 
your webapp, with the top directory (e.g. CATALINA_BASE/webapps/abc if 
your application is called "abc"), a WEB-INF subdirectory, the class 
files or jars, etc.., OR of a single "war" file containing everything 
and named "abc.war".
- if it is a war file "abc.war", the simple fact of dropping it in the 
"webapps" directory will make it so that Tomcat will notice it, and 
"deploy" it as the application named "abc".
You should then be able to access this application by entering the URL : 
"http://myhostname/abc".
- if you want your application to be the /default/ application for that 
Host (in other words, the one that is called when the user enters 
"http://myhostname/"), then you should name your application "ROOT" 
(exactly like that, in capitals), and place it under the "webapps" 
directory of that Host.
If it is a war file, then it should be named ROOT.war (also exactly).


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org