Sorry about all these posts....I could have just been patient and combined
them.  :0)

Did you delete the default contexts?  This will cause this problem. Either
reinstall them temporarily or look into your config files in tomcat to clear
up the issue. Sorry, I don't have time to look them up right now.

Regards,
Craig

-----Original Message-----
From: Craig O'Brien [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 21, 2001 3:20 PM
To: [EMAIL PROTECTED]
Subject: RE: cpu load 100% on windows 2000 using iis


Just so you know.  This is not a Windows only issue and can appear on most
OSs. (Solarus etc.)

Craig

-----Original Message-----
From: Rui M . Silva Seabra [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 21, 2001 2: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]

Reply via email to