Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 7316 invoked from network); 1 Jan 2001 12:35:51 -0000 Received: from manna-fw.ser.netvision.net.il (HELO fwsys) (212.143.111.1) by h31.sny.collab.net with SMTP; 1 Jan 2001 12:35:51 -0000 Received: from fwsys ([207.232.44.113]) by dns.mannanetwork.com (8.9.3/8.8.7) with SMTP id OAA21597 for ; Mon, 1 Jan 2001 14:44:05 +0200 From: "David Soroko" To: Subject: The significance of root context Date: Mon, 1 Jan 2001 14:37:02 +0200 Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0000_01C073A4.CCCA61A0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: <40BA50B279BED411A01300805F0DEBBA141BE4@ICICISHANTI> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N ------=_NextPart_000_0000_01C073A4.CCCA61A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit I am trying to understand the significance of the "root" context in TC 3.2. It seems that when no root context is defined i.e. when nothing is mapped to "" path and an unavailable resource is requested by a client, tomcat takes up 100% CPU time and does not let go. Must I always map some directory to the root context? Steps to reproduce behavior in the standard TC 3.2 distribution: * In server.xml comment out (this has the effect that the webapps/ROOT is not mapped to ""). * Start TC * Connect to http://localhost:8080 Note: the same behavior can be seen if webapps/ROOT is removed. -- ============================================ David Soroko mailto:davids@mannanetwork.com http://www.geocities.com/SiliconValley/Campus/1628/ Manna Inc. ============================================ ------=_NextPart_000_0000_01C073A4.CCCA61A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable The significance of root context

I am trying to understand the significance of the = "root" context in TC 3.2.

It seems that when no root context is defined i.e. = when nothing is mapped to "" path and
an unavailable resource is requested by a client, = tomcat takes up 100% CPU time and does not let go.


Must I always map some directory to the root = context?




Steps to reproduce behavior in the standard TC 3.2 = distribution:

* In server.xml comment out
<ContextInterceptor = className=3D"org.apache.tomcat.context.AutoSetup" />

(this has the effect that the webapps/ROOT is not = mapped to "").

* Start TC

* Connect to http://localhost:8080

Note: the same behavior can be seen if webapps/ROOT is = removed.





--

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
David Soroko
mailto:davids@mannanetwork.com
http://www.g= eocities.com/SiliconValley/Campus/1628/
Manna Inc.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=

------=_NextPart_000_0000_01C073A4.CCCA61A0--