Connection Pool Issue

[Guadala Harry]

I have an ASP.NET/C# app that connects to SQL Server 2000. I recently
started getting the following error message during development (i.e., when
launching the app from the VS.NET 2003 IDE):

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 found that closing and re-opening VS.NET clears things up. What's
going on? What can I do to prevent this? Am I doing something bad? I thought
the connection pool manages itself and recycles connections as necessary.

Thanks,

GH

[bruce barker]

your app has connection leaks, meaning it opens connections but does not
close them. common problem if your use datareaders.

-- bruce (sqlwork.com)

"Guadala Harry" <Ch*********@gh.com> wrote in message
news:#h*************@TK2MSFTNGP12.phx.gbl...

I have an ASP.NET/C# app that connects to SQL Server 2000. I recently
started getting the following error message during development (i.e., when
launching the app from the VS.NET 2003 IDE):

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 found that closing and re-opening VS.NET clears things up. What's
going on? What can I do to prevent this? Am I doing something bad? I thought the connection pool manages itself and recycles connections as necessary.

Thanks,

GH

[Rob T]

You are forgetting to close your connections. I had the same problem...make
sure you always close them before leaving a function or navigating to
another page.

"Guadala Harry" <Ch*********@gh.com> wrote in message
news:%2***************@TK2MSFTNGP12.phx.gbl...

I have an ASP.NET/C# app that connects to SQL Server 2000. I recently
started getting the following error message during development (i.e., when
launching the app from the VS.NET 2003 IDE):

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 found that closing and re-opening VS.NET clears things up. What's
going on? What can I do to prevent this? Am I doing something bad? I thought the connection pool manages itself and recycles connections as necessary.

Thanks,

GH