Timeout expired. Connection pooling

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am in the process of moving an ASP.NET app from my development machine to a
web server. I am getting the following error message:

Message: "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."

Is this indicative of a coding problem or perhaps a setting on the server?

Help is appriciated

LRK
 
I am in the process of moving an ASP.NET app from my development machine to
a
web server. I am getting the following error message:

Message: "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."

Is this indicative of a coding problem or perhaps a setting on the server?
Click to expand...

It depends on what connection type you're using. Can you be more specific
about connection type your creating, is it database connection? Or is it
some other type of connection?
 
Ok, See when you are using connection pooling feature in your web
application, the application maintains the pool of db connections. Now lets
suppose new connection is requested it is given from the connection pool, if
all connections in pool are in open state then one new connection is created
and return it to your application and added to pool. But if your connection
pool is full then application will wait for the any of connections in pool to
get free, it seems that your pool is full and no connection is releasing.
Check it thoroughly, as some thing is screwedup in ur code .. either you are
not closing datareader after reading data or not doing connection.close()
 
Most likely a coding problem.

Normally when creating web pages a database connection will be open for
a split second. That means that each connection in the pool can be used
to create several web pages per second. The default size of the
connection pool for SqlConnection, for instance, is 100. That means that
there are connections enough to create thousands of pages per second.
The default timeout for SqlConnection is 15 seconds, which means that
there would have to be several thousands of requests queued up in order
to exhaust the connection pool under normal circumstances.

Use the Dispose method on all database connections (this will also close
the connection). You have to close any DataReader you use, or it will
keep the connection object active.
 
Back
Top