One of our servers has been slowed to a crawl over the past week. We've finally identified the problem: it's only running 12 threads in its thread pool, but the processors are not maxed out. Effectively half of the srever is sitting idle while clients wait to get serviced! I've set the ProcessorThreadMax to 30 (it's a dual-processor box), set the ThreadCreationThreshold to 5, and the RequestQueMax to 60, yet thenumber of threads in the pool remains pegged at 12. Any ideas? The processor utiliization is around 60% for each processor-- not nearly maxed out. There's no reason that I can think of why more threads are not being created. Any ideas? #549 - 1997.10.21
In IIS 3.0 when I invoke the ASP RoadMap icon on my pc, the page comes up but the "Contents" frame on the left is entirely black, except for the book gifs. What's going on?
Also, Nearly everytime I invoke IE40, It hangs there with a blank view and just behind it, I get a Locate Link Dialog box. This usually happens when I clik on a link when IE is not already invoked. What I do is hit cancel in the dialog box, then hit the link again and then the page comes up!
I'm under the impression that IIS 1.0, 2.0, 3.0 uses a thread pool to handle incoming requests and for low activity the same threads are just reused over and over again. However, if I create a bad ISAPI application that sits in an infinite loop will IIS create more and more threads? #461 - 1997.07.12
Is there a way to override the 404 error in IIS 1.0, 2.0 , or 3.0? I would like to have a page come up listing the web sites on our server when that error happens. #460 - 1997.07.12
