Troubleshooting MySQL Connector/NET connection pool issues requires a careful balance between client-side C# configurations and server-side MySQL variables. When connection pooling is mismanaged, applications suffer from hanging requests, sudden performance drops, or total database crashes. 1. Connection Pool Exhaustion (Timeout Errors)
The Symptom: The application throws MySqlException: The timeout period elapsed prior to obtaining a connection from the pool.
The Root Cause: This happens because all pooled connections are actively in use, and the pool has already scaled to its Max Pool Size. The driver blocks the current thread until another query completes, eventually timing out. How to Troubleshoot & Fix:
Enforce Block Disposals: Ensure every single MySqlConnection and MySqlDataReader object is wrapped in a C# using block or statement. This guarantees that connections return to the pool immediately upon completion or when exceptions occur.
Never Use Global Connections: Do not create a single, globally shared instance of MySqlConnection to manually open and close across different threads.
Increase Max Pool Size: If your application architecture naturally handles massive concurrent traffic, safely bump your connection string’s default threshold by adding Max Pool Size=200;. 2. Zombie and Sleep Connections (Leaky Pools) Connection pool leak when connect time out #947 – GitHub