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
