S
Steve Harris
I'm getting the following error message in an ASP.NET application:
Time 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.
I've read several KB articles on this and examined the server through the
performance monitor while this error was occurring.
SqlClient: _global_ Current # connection pools: 6
SqlClient: _global_ Current # pooled & nonpooled connections: 14
SqlClient: _global_ Current # pooled connections: 14
We do have six different apps running each with its own connection string.
The connection strings contain only the server, database uid and pwd
keywords. So I think I understand the Current # connection pools.
What I do not understand is how I'm running out of connections when there is
only 14 being used/pooled when the default is 100? What am I missing here?
Also, as a side note, does anyone know what the "SqlClient: Total # failed
commands" represents? This number was in the thousands on the performance
monitor but I cannot see anything in our log file. We do capture and log
every failed execution for review and there was nothing reported.
Thanks in advance.
Steve
Time 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.
I've read several KB articles on this and examined the server through the
performance monitor while this error was occurring.
SqlClient: _global_ Current # connection pools: 6
SqlClient: _global_ Current # pooled & nonpooled connections: 14
SqlClient: _global_ Current # pooled connections: 14
We do have six different apps running each with its own connection string.
The connection strings contain only the server, database uid and pwd
keywords. So I think I understand the Current # connection pools.
What I do not understand is how I'm running out of connections when there is
only 14 being used/pooled when the default is 100? What am I missing here?
Also, as a side note, does anyone know what the "SqlClient: Total # failed
commands" represents? This number was in the thousands on the performance
monitor but I cannot see anything in our log file. We do capture and log
every failed execution for review and there was nothing reported.
Thanks in advance.
Steve