connection timeout

I tend to get the following error:

"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 checked my connections in profiler and noticed my SPID's tend to
hang around even after I close a connection.

Does anyone have any ideas/thoughts as to what I could be doing wrong
here?

I typlically just use the sqlconnection.close method.

Thanks

Are your sure that your data access functions all close the connection, as
this is one of the most common errors.

--
( OHM ) - One Handed Man
AKA Terry Burns - http://TrainingOn.net


"sam" <samir.kothari01@gmail.com> wrote in message
news:1144458932.085631.216120@g10g2000cwb.googlegroups.com...
>I tend to get the following error:
>
> "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 checked my connections in profiler and noticed my SPID's tend to
> hang around even after I close a connection.
>
> Does anyone have any ideas/thoughts as to what I could be doing wrong
> here?
>
> I typlically just use the sqlconnection.close method.
>
> Thanks
>

See my SQL Server Magazine article on managing the connection pool. It
summarizes the discussions we've had over the years.
http://www.betav.com/sql_server_magazine.htm


--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________

"sam" <samir.kothari01@gmail.com> wrote in message
news:1144458932.085631.216120@g10g2000cwb.googlegroups.com...
>I tend to get the following error:
>
> "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 checked my connections in profiler and noticed my SPID's tend to
> hang around even after I close a connection.
>
> Does anyone have any ideas/thoughts as to what I could be doing wrong
> here?
>
> I typlically just use the sqlconnection.close method.
>
> Thanks
>