IISState.log - Slow Performance on IIS 6 (SBS2003 SP1)

Hi there,

We have a Classic ASP application that has been running on an XP IIS5.1 box
for 2 years without any issues (uses SQL2005 Express as data store).

We have a new SBS2003 SP1 installation and have migrated the Classic ASP
application to it with its own application pool using default settings.
Intermittantly the application's performance degrades dramatically with most
pages timing out.
No excessive CPU or memory utilization is evident and there is nothing in
the eventlogs to suggest any problems. The IIS6 htperr1.log contains a
multitude of "Connection_Dropped manunetapplicationpool" entries for various
ASP pages. Performing an IISRESET or recycle of the Application Pool
temporarily resolves the problem. This slowdown is occuring daily and
renders the application unusable.

I have taken an IISState dump when the web application goes into slowdown =>
http://www.russellchapman.com.au/iisstatelog.htm

This is a real problem for us and I was hoping someone could take a look at
the dump and hopefully give me an idea on what maybe causing this?


Regards,
Russell.

Re: IISState.log - Slow Performance on IIS 6 (SBS2003 SP1)

Whenever one gets slow performance but there is no excessive CPU, RAM,
Error messages, etc, I start suspecting lock contention of some common
resource shared amongst the affected web pages.

Unfortunately, I do not see anything unusual nor bad in your IIS State
logs. No thread hogged a lot of CPU time, no threads were competing for
a lock, no excessive number of threads, and most were sitting around
idle.

You could tell IIS6 to schedule a daily recycle of the ASP
application's Application Pool as a temporary work-around, to buy
yourself more time to figure out what is truly wrong. You should not
need to use IISRESET.


//David
http://w3-4u.blogspot.com
//



RussellC wrote:
> Hi there,
>
> We have a Classic ASP application that has been running on an XP IIS5.1 box
> for 2 years without any issues (uses SQL2005 Express as data store).
>
> We have a new SBS2003 SP1 installation and have migrated the Classic ASP
> application to it with its own application pool using default settings.
> Intermittantly the application's performance degrades dramatically with most
> pages timing out.
> No excessive CPU or memory utilization is evident and there is nothing in
> the eventlogs to suggest any problems. The IIS6 htperr1.log contains a
> multitude of "Connection_Dropped manunetapplicationpool" entries for various
> ASP pages. Performing an IISRESET or recycle of the Application Pool
> temporarily resolves the problem. This slowdown is occuring daily and
> renders the application unusable.
>
> I have taken an IISState dump when the web application goes into slowdown =>
> http://www.russellchapman.com.au/iisstatelog.htm
>
> This is a real problem for us and I was hoping someone could take a look at
> the dump and hopefully give me an idea on what maybe causing this?
>
>
> Regards,
> Russell.

Anything?

Hi Russell,
Did you ever get to the bottom of this?
I am having an identical issue.
Steve
steve@dangerfield.biz


EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com

Re: Anything?

On Aug 2, 6:59 pm, steve dangerfield wrote:
> Hi Russell,
> Did you ever get to the bottom of this?
> I am having an identical issue.
> Steve
> st...@dangerfield.biz
>
> EggHeadCafe.com - .NET Developer Portal of Choicehttp://www.eggheadcafe.com


You don't really have an identical issue. You just have generic
symptoms that sound similar but can be caused by many, many things.
Getting a stack backtrace during the issue is the best way to discern
what is going on.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//