Our investigation revealed that the .NET SQLConnection Connection Pool is - at Connection Timeout (Default 4 hours) - doing something that seems to be statistical analysis - and during this analysis - no more connections can be retrieved from the pool. In our case we are using a connection from the pool 5 times a second. When the pool statistical analysis runs - it is analysing 5 * 60 * 60 * 4 (Hours) worth of statistical data. This process takes about 20 minutes. 20 minutes where the pool is unavailable !!! Solution - make the timeout about 30 seconds so that the analysis has a lot less data to analyse - and then the lag created by this analysis is one hellova lot shorter and has virtually no impact.
i.e. Add ";Connection Lifetime=30" to your connection string. Timeout is now 30 seconds.
**********************************************************************
Sent via Fuzzy Software @
http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...