Automatically recycle application pool on an error and figuring out why app is failing
Posted on 2004-07-30
I am new to dealing with IIS as a web server (I miss Apache :() and I am trying to get used to this application pool thing. Now, I understand that if a process starts taking too many resources, rapid application recycling will disable the process after a set amount of times.
My question is, I am trouble shooting an ASP web page, where if you recycle the application pool, it automatically starts working again. Rapid Application Recycling does not appear to be the problem because the pool is still active before I recycle it. Is there a way to recycle the application pool automatically so that it doesn't have to manually be done and so that ASP pages won't break?
Also, what can be the cause of these symptoms? Is it most likely bad ASP code? If so, how would I even go about trouble shooting what code is causing the problems?