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