M
Mark Rae
Hi,
According to an MSKB article
(http://support.microsoft.com/default.aspx?scid=kb;en-us;314429), there is a
bug in PerfMon whereby certain counters are not reset correctly.
I need to stress test an ASP.NET solution with specific respect to
performance and connection pooling.
The client is pretty certain that all SqlConnection objects are being closed
and disposed correctly - and, looking at the code, this certainly appears to
be the case - but is experiencing lots of the dreaded "The timeout period
elapsed prior to obtaining a connection from the pool. This may have
occurred because all pooled connections were in use and max pool size was
reached." errors.
Strangely, though, even with the reported bug in PerfMon, this appears to be
happening way before the max pool size (100) is reached - typically around
50-60 pooled connections...
Can anyone recommend a good utility for monitoring this instead of PerfMon?
Any assistance gratefully received.
Mark
According to an MSKB article
(http://support.microsoft.com/default.aspx?scid=kb;en-us;314429), there is a
bug in PerfMon whereby certain counters are not reset correctly.
I need to stress test an ASP.NET solution with specific respect to
performance and connection pooling.
The client is pretty certain that all SqlConnection objects are being closed
and disposed correctly - and, looking at the code, this certainly appears to
be the case - but is experiencing lots of the dreaded "The timeout period
elapsed prior to obtaining a connection from the pool. This may have
occurred because all pooled connections were in use and max pool size was
reached." errors.
Strangely, though, even with the reported bug in PerfMon, this appears to be
happening way before the max pool size (100) is reached - typically around
50-60 pooled connections...
Can anyone recommend a good utility for monitoring this instead of PerfMon?
Any assistance gratefully received.
Mark