Re: The significance of root context

[Shawn McMurdo]

Did you see my patch submitted to the list on 2000 Dec 23?
I think it addresses this problem.
Shawn

David Soroko wrote:

 Thanks --

============================================
David Soroko
mailto:[EMAIL PROTECTED]
http://www.geocities.com/SiliconValley/Campus/1628/
Manna Inc.
============================================
 

-----Original Message-----
From: Thom Park [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 02, 2001 1:42 AM
To: [EMAIL PROTECTED]
Subject: Re: The significance of root context
 

This is a known bug in tomcat and is documented in the release notes - I got bit by this one as well ;-)

-T.

David Soroko wrote:

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="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.
 
 
 

--

============================================
David Soroko
mailto:[EMAIL PROTECTED]
http://www.geocities.com/SiliconValley/Campus/1628/
Manna Inc.
============================================

--
Shawn McMurdo              mailto:[EMAIL PROTECTED]
Lutris Technologies        http://www.lutris.com
Enhydra.Org                http://www.enhydra.org