We're deploying our .net application and ran into the error: Function exception: 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. We have our connection timeout set to 60 seconds. We also properly close our connection immediately after each data select or insert. At 3:30 PM today, we experienced the above error. We were unable to perform any DB operations for a period of 30 minutes on our site (Although we were able to connect to the DB with SMS). Since the SQL DB is on a shared server, is there any mechanism in place to prevent those with poor coding practice from using all of the connections in the pool? If so, how many connections is each DB instance/site allocated. Thanks.
This means that your application used up all the database connection. Typically it is caused because your application is not closing the database connection correctly. Recycle your application pool and it should clear it up. Remember if you are not closing your database connections correctly this will potentially happen again.
