Stefan,
Tomcat expects there to be some configuration for the "root" context - that is, any
resource directly under "/". An example would be "/index.html". This is as opposed to
an application context such as "/myapp/index.html".
The default install has a "ROOT.war" file. It seems that anything in that directory
("ROOT" - all caps), if it exists under the webapps directory, will be used for
anything requested in the root context. If that directory doesn't exist, ***and*** if
no other directory has been explicity specified for the root context in server.xml,
then you'll see this CPU spinup.
As an example, in our server.xml, we have specified the root context as:
<Context path="/" docBase="web/nosuchdir" debug="0" reloadable="false" >
</Context>
Since there is no relative directory named "web/nosuchdir", anything requested under
"/" will return a "Not Found" error.
Hope that helps,
Donnie
>>> [EMAIL PROTECTED] 03/22/01 11:54AM >>>
Donnie,
thank you for your hint. I have experienced similar problems with solaris 8 and
tomcat 3.2.1. However I regret that I do not understand the mentioned problem:
> 6.11 Misconfiguration Can Cause CPU-Bound Loop
>
> If you misconfigure Tomcat 3.2 in a way that there is no valid context to
> handle a request (such as removing the root context and then attempting a
> request that should be handled by that context), Tomcat will enter a CPU-bound
> loop instead of responding with a 404 error.
>
> Workaround: kill the offending Tomcat process and correct your server.xml
> file such that there is a properly configured root context.
Could anyone perhaps give an illustrative example ?
TIA
*stefan
