Last post May 28, 2013 02:31 AM by Topspy
May 22, 2013 01:19 AM|pal.sandip005|LINK
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.
Please advise me.........
May 22, 2013 01:28 AM|itsmemuthu|LINK
May 27, 2013 10:00 PM|Angie xu - MSFT|LINK
Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool.
This problem occurred most probably because of connection leak. Either the connection string do not close properly or consistently.
When you intend to close your database connection, you want to make sure that you are really closing it. The following code looks fine yet causes a connection leak,
Some solutions that you can try to solve the problem:
1) Check your application to make sure all database connections are closed when it is not needed. ASP.NET is supposed to have garbage collector to reclaim unused resource. However, on a busy site, it is likely that the connection pool will run out of connections
before garbage collection kicks in.
2) You can raise the connection pool size in the connection string. For example, you can add "Max Pool Size=100" to your connection string to increase the pool size to 100.
For further information, you could refer our msdn blog about
Max pool size was reached,
hope it helps you,
May 28, 2013 02:31 AM|Topspy|LINK
Good points from Angie xu. You also need to check if you have assigned too little memory to the app pool.