craigmcc 00/11/27 15:36:49
Modified: src/doc Tag: tomcat_32 readme
Log:
Document the fact that a particular misconfiguration of Tomcat can cause
a CPU-bound loop to occur.
Revision Changes Path
No revision
No revision
1.8.2.8 +11 -1 jakarta-tomcat/src/doc/readme
Index: readme
===================================================================
RCS file: /home/cvs/jakarta-tomcat/src/doc/readme,v
retrieving revision 1.8.2.7
retrieving revision 1.8.2.8
diff -u -r1.8.2.7 -r1.8.2.8
--- readme 2000/11/27 22:47:58 1.8.2.7
+++ readme 2000/11/27 23:36:45 1.8.2.8
@@ -1,4 +1,4 @@
-$Id: readme,v 1.8.2.7 2000/11/27 22:47:58 craigmcc Exp $
+$Id: readme,v 1.8.2.8 2000/11/27 23:36:45 craigmcc Exp $
Release Notes for:
==================
@@ -310,4 +310,14 @@
<Context path="/ctx" docBase="r:\path" />
where "r:" is mapped to this share.
+
+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.
