Timeout expired

R

Roz Lee

I am continually experiencing this error message while developing and
test a
simple .net application.

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.

This has only started happening since installing 1.1. I have checked
every connection to be sure it is being closed after executing my
queries. I have tried reading everything I can about connection
pooling. Nothing helps. I have tried monitoring using Performance
Counters but the .NET CLR Data performance counters seem to accumulate
and are not a correct reflection.

Can anyone help me please?
Thanks
Ros Lee
 
W

William \(Bill\) Vaughn

Are you using the DataReader or Just Fill/Update? Are you using
ExecuteNonQuery or ExecuteScalar?

--
____________________________________
Bill Vaughn
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.
__________________________________
 
R

Ros Lee

All of those at different times.
When using datareaders I always close the connection and the datareader
explicitly after use.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Timeout expired connection 2
connection status "suspended" 2
Monitoring connection pooling between .NET 1.1 & SQL Server 2000 2
connection timeout 2
Timeout - max pool size reached 7
Timeout Expired on first System.Data.Common.DbDataAdapter.Fill 3
ado.net, connection pooling, and leaked connections 8
All Pooled Connections In Use 4

Top