There is a known issue. It appears that you must insure that Tomcat only
operates in a valid context. I have not faced this issue so I don't have any
suggestions, however, this may be helpful.
Here is a snippet from a past discussion on this issue:
/*
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.
*/
Hope this helps,
Craig
> -----Original Message-----
> From: Rui M . Silva Seabra [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 21, 2001 4:35 PM
> To: [EMAIL PROTECTED]
> Subject: cpu load 100% on windows 2000 using iis
>
>
> Hello,
>
> Please, before reading this, bare in mind that unfourtunately I
> am forced to use an IIS and windows 2000, because of a client's
> demands, so changing to the desirable *nix+apache+tomcat is not an option.
>
> Apparently everything is okay.
> Until the moment when you either reach the isapi_redirect.dll
> directly (because you know the url and there's no point in
> defending security by obscurity) or call a servlet.
> By the time either of this events happen, the tomcat java
> process jumps to 100% cpu usage, until an indeterminate time, and
> provides no results.
>
> So, what could be happening? Here go some technical details on
> the machine:
>
> * windows 2000 (yuk)
> - no namesolver, all name must be solved by usage of the hosts file
> * IIS (default with win2k - yuk yuk)
> * tomcat 3.2.1
> * jdk 1.3.0
>
>
> If anyone has a sensible opinion on this matter, please, share
> your thoughts with me on the list, since this could be a future
> trouble shooter.
>
> Hugs, rms
>
> --
> + No matter how much you do, you never do enough -- unknown
> + Whatever you do will be insignificant,
> | but it is very important that you do it -- Ghandi
> + So let's do it...?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
