It simply hungs. That's all... I've been inspecting everything but found nothing. In order to make it work again I have to restart the IIS or sometimes it helps only to kill the asp worker process.
The memory is stable (not allocating or de-allocating memory), and both the processors are about 99% free (it is a dedicated machine, nothing else runs there).
The processModel has autoConfig="true" so all the values are the default ones (and I'm refering to maxIoThreads, maxWorkerThreads, minIoThreads,minWorkerThreads, requestQueueLimit and responseDeadlockInterval). The IIS ver. is 6 (win2k3 server o.s.).
It is across all ASP.NET applications, meaning that when it happens, none of the other ASP.NET apps is responding (they behave just like the requests are not relayed to the apps anymore). And it is intermittent, which makes this a tough one.. It happens every few days, sometimes once a week.
One more detail, which seems to be common to all situations: the failure never occurs while you are in the application. Only when you open the browser, type in the address, hit enter, and expect to see the login page...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.