tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Soroko" <>
Subject The significance of root context
Date Mon, 01 Jan 2001 12:37:02 GMT
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
Manna Inc.

View raw message