« Previous Next »

• 07-09-2007, 4:49 AM

  onn Joined on 07-01-2007, 10:25 AM Posts 3

  Troubleshooting misbehaving application pools Reply Contact Hi, I was wondering whether there are some general guidelines or best practices for troubleshooting misbehaving applications on a  shared application-pool scenario. I'm currently hosting around 50 sites all residing on a single app pool (1.1 framework) and it seems that from time to time the app pool hangs probably due to some code in the web site. I've been unsuccesful trying to pinpoint the site that is probablly causing the hang. I did notice that around the time the sites suddenly become unavailable there's an asp.net request queue starting. I thought about isolating the web sites each on it's own app pool but was wondering if there are any best practices for this type of troubleshooting.  Thanks. Onn

  Tags: asp 1.1 iis dotnetasp.netiisIIS 6multiple sites

• 07-09-2007, 9:03 AM

  In reply to

  tomkmvp Joined on 03-20-2003, 6:27 AM Central NJ Posts 6,222	Re: Troubleshooting misbehaving application pools Reply Contact That would be a start.  Give Debug Diagnostics a try too: http://www.iisdiagnostics.com/ Tom Kaminski IIS MVP http://mvp.support.microsoft.com/ http://blogs.iis.net/tomkmvp/ http://www.linkedin.com/pub/8/690/408 http://www.bluesrepublic.org/

• 07-11-2007, 12:23 AM

  In reply to

  steve schofield Joined on 06-10-2002, 8:54 PM MI Posts 3,945

  Re: Troubleshooting misbehaving application pools Reply Contact Isolating websites in their own application pools is a good idea, and a good place to start.  I usually search the filesystem for changed webpages or config files when things go haywire, this could be a good lead.  Steve Schofield Windows Server MVP - IIS http://weblogs.asp.net/steveschofield http://www.IISLogs.com Log archival solution Install, Configure, Forget