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.
LRK wrote:
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