Recently, I began to encounter problems connecting to a database with SQL Server on my development machine.
System.InvalidOperationException: Timed out. Waiting period before receiving a connection from the pool
How can I control the connection pool to find out what is happening?
Additional Information:
I was not lucky with this - I am definitely not leaking connections. Each connection is inside a using statement.
When the problem occurs, I have the Performance Monitor window open and it does not appear anywhere near the pool limit (which is 100) - usually about 2 - 5 connections, so I donβt think the pool is exhausted, so maybe this is a timeout .
However, I set ConnectionTimeout to 0 - which, according to the documentation, means that it has to wait forever to connect, but I don't see it.
When this happens, it happens pretty quickly - I start under the debugger from VS2010 - launch a new instance of my application - and this can happen within a second or two from launch - when the application starts, there are several requests that occur. The actual SQL Server I came across is SQL Express 2008. Maybe I should try running it with SQL Server 2008 and see if I see any other behavior.
Any other ideas?
source share