StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POWhat can cause InvalidOperationException: max pool size reached except for the obvious
text
Body
copied!<p>I have an issue with a windows service that accesses a SqlServer 2005 database. Every Monday it crashes with an InvalidOperationException: 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.</p> <p>I've checked all the obvious things like closing the db connections and readers and found no problems. </p> <p>The strangest thing is that in the last case I set up perf monitor to record the number of connections in the pool and things like that and found that the Sql Server actually went down a few days before the service crashed, so all the SQL counters showed 0 (the service handles SQL Server stopping and tries to connect every few seconds until it reconnects successfully). </p> <p>Before the SQL server was stopped, the amount of open connections was 1-2 all the time, so it really doesn't seem to be a problem with the connection count. </p> <p>I'll be investigating the SQL Server logs for clues, but maybe you can give me an idea about what might be causing this exception if the actual number of connection is not a problem.</p> <p>Update:</p> <p>Checked the logs and it seems that the Sql Server wasn't down all the time. On Thursday it was stopped, but was restarted on Friday. The restart caused the SQL counters in perf mon to stop reporting data, so I have no real data about the number of connections at the time of the crash.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload