quote:

---

Ever single connection I make to the database is explicitly closed immediately after use. Every datareader, command object and datadapter are set to null.

---

This reminds me that in the .NET Framework, most objects are not reclaimed when the Dispose() method is called, or they are set to NULL/Nothing. Most resources are cleaned up when the Garbage Collector is invoked. This happens only when the application starts to run out of memory, but it can be manually invoked by calling GC.Collect(). There is a teeny-weeny chance this might help solve the problem, you might want to try it (my fingers are crossed )

OS

quote:

---

post your code.

---

quote:

---

Originally posted by label

There was a Bug in the 1.0 .NET framework that would cause the following error to occur if you had any decent amount of activity on your ASP.NET applications that was apparently solved with the 1.0 Service Pack 2. (Though I don't know this first hand, it's what I read here).

"Timeout expired. 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. "

I've seen a bunch of people on various boards with this issue and I've yet to see on definitive response on how to solve this problem.

Ever single connection I make to the database is explicitly closed immediately after use. Every datareader, command object and datadapter are set to null. Still we get this problem with just a little bit of use.


We're using 1.1 and connection to a SQL2000 DB using the latest MDAC. I believe we are doing everything we can programmatically which leads me to believe that this is another (large) bug in the 1.1 framework or it's just a poorly designed aspect of it as quite a few people have issues with it and there doesn't seem to be a good way of fixing the problem that I can find after 2 days of research.

As this has alot to do with ADO/SQL I thought perhaps some of you here might have some insights.

Thanks

---