Posted by Erland Sommarskog on 06/02/05 23:43

MrDom (mr_dom_is@hotmail.com) writes:
> We had to disable connectioning pooling on our ASP.Net 2002 and ASP.Net
> framework 2003 applications becuase we got intermittent errors about
> the connectionpool running out and there was no actual way to get rid
> of it.
>
> For the record we were closing and disposing of out connection objects
> properly but despite this, we would get the dreaded erorr unexpectedly,
> and have to reset the server to sort it out.

Nevertheless, it's was a hole in your application, not in ADO .Net. If
memory serves, I think the common error is to not close the command
object before you close the connection.

Bill Vaugbn had some good articles on the ADO .Net connection pool
in the May and July 2003 issues of SQL Server Magazine. See
http://www.windowsitpro.com/Article/ArticleID/38356/38356.html and
http://www.windowsitpro.com/Article/ArticleID/39031/39031.html.
(The second article is for subscribers only, but the first is
publically available.)

--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp

[Back to original message]