The timeout has expired, but the connection has not yet been taken from the pool.

Little scum · Posted on 4/29/2019 3:50:02 PM

Unhandled exception: System.InvalidOperationException: The timeout has expired. The timeout has expired, but the connection has not yet been taken from the pool. This may be because all pool connections are in use and the maximum pool size has been reached.

This may occur because all pool connections are in use and the maximum pool size is reached.

Solution:

The first thing to do is close the connection as soon as we use it. If the connection is not closed, then the connection is saved to the connection pool and the GC is known to be destroyed. In this case, you think that the connection pool has not reached the maximum value, but in fact the connection pool has reached the maximum value, secondly, we can use the Max Pool Size = N in the connection string; to dynamically expand the maximum number of connections in the connection pool.

Illustrate:

That is, if the value of max pool size is not specified in the connectionString,Then max pool size=100If the number of visitors to the database is 101, the above error will appear if there is still no available Connection after waiting for the time set by SqlConnection.ConnectionTimeout (default is 15 seconds).

When we set to:

Login is visible.

If the number of visitors connecting to the database at the same time is 513, the above error will occur if there is still no available Connection after waiting for the time set by SqlConnection.ConnectionTimeout (default is 15 seconds).

qhdedu · Posted on 4/30/2019 5:11:45 PM

Prompt:Authors are banned or removed content is automatically blocked

[Source] The timeout has expired, but the connection has not yet been taken from the pool.

Related Posts

Sections viewed

qhdedu	Posted on 4/30/2019 5:11:45 PM \| Prompt:Authors are banned or removed content is automatically blocked
qhdedu