TimeoutException caused by connection pool exhaustion in EF Core

Question

Problem
In a high‑concurrency ASP.NET Core application using EF Core 8, a TimeoutException occasionally bubbles up from DbConnection.Open. The exception stack shows the ADO.NET provider throwing due to the underlying connection pool being exhausted. The application uses DbContextPool with default settings, and the connection string contains Pooling=true;Max Pool Size=100. The errors appear intermittently, not consistently on every request.
Constraints & Uncertainty
The exact cause of the pool exhaustion is unclear. Possibilities include:

Transient spikes in request volume that briefly exceed the pool size.
Improper disposal of DbContext instances leading to leaked connections.
Interaction between EF Core’s internal pooling and the ADO.NET pool limits.

There is no current telemetry on pool usage or connection churn, and the application’s transaction scopes vary between short and long operations.
Key Questions

What ADO.NET and EF Core metrics should I monitor to confirm that the pool is being exhausted?
How can I distinguish between a genuine connection‑pool timeout and a different transient network error in the exception stack?
What best‑practice adjustments to DbContextPool configuration or connection string settings can mitigate intermittent pool exhaustion?

Siddharth · Answer

Direct Resolution
A TimeoutException occurring during DbConnection.Open is an ADO.NET provider error, not an EF Core internal failure. It indicates that the application requested a connection, but all 100 connections in the pool were in use, and the request timed out while waiting for one to be released.

Confirming Pool Exhaustion vs. Network Errors
To distinguish pool exhaustion from transient network faults, examine the exception message and inner exceptions:

Pool Exhaustion: The message explicitly mentions that the timeout period expired while attempting to get a connection from the pool (e.g., "Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool").
  Network Error: The stack trace typically wraps a SocketException, a DNS resolution failure, or a provider-specific error code indicating a lost connection or a server-side reset.

Monitoring and Metrics
To confirm the pool is hitting its limit, monitor the following:

Provider EventCounters: Use dotnet-counters to monitor active connection counts. If the active count plateaus at 100 (your Max Pool Size) during the spikes, exhaustion is confirmed.
  EF Core Logging: Enable Information level logging for Microsoft.EntityFrameworkCore.Database.Connections. Correlate ConnectionOpened and ConnectionClosed events with the timestamps of the TimeoutException.
  Server-Side State: Query the database server (e.g., sys.dm_exec_connections in SQL Server) to see the number of active sessions originating from the application's IP.

Mitigation Strategies
Since DbContextPool reuses the DbContext object but does not keep the underlying database connection open between requests, increasing the context pool size will not fix ADO.NET pool exhaustion. Instead, apply these adjustments:

Increase Max Pool Size: If your database server can handle the load, increase Max Pool Size=200 (or higher) in the connection string to accommodate transient concurrency spikes.
  Audit Transaction Duration: Ensure that long-running operations (e.g., calling an external API while a transaction is open) are moved outside the DbContext scope. Connections are held until the transaction completes or the context is disposed.
  Verify Disposal: Ensure DbContext instances are registered as Scoped in ASP.NET Core DI. If you are manually creating contexts via a factory, verify they are wrapped in using blocks.

Required Diagnostic Detail
To refine this recommendation: Are you using TransactionScope or explicit IDbContextTransaction blocks that wrap asynchronous calls to external services? If so, the connections are being held open far longer than the database work requires, which is the most common cause of pool exhaustion in EF Core.

TimeoutException caused by connection pool exhaustion in EF Core

Problem

Constraints & Uncertainty

Key Questions

1 answer

Direct Resolution

Confirming Pool Exhaustion vs. Network Errors

Monitoring and Metrics

Mitigation Strategies

Required Diagnostic Detail

Your perspective belongs here.

0 question comments