Bug #61715 MySql.Data [Complete Loss of Service]
Submitted: 1 Jul 2011 2:21 Modified: 1 Jul 2011 3:21
Reporter: Gareth Jensen Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server: Locking Severity:S1 (Critical)
Version:All (Current Test: 6.4.2) OS:Windows (Windows 7 SP1)
Assigned to: CPU Architecture:Any
Tags: locking, MySql.Data, pool, problems

[1 Jul 2011 2:21] Gareth Jensen 
Description:
Error type is "0" - Message is "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 the max pool size was reached."

This is my connection string:
"Server=localhost; Database='database'; Username='root'; Password='password'; Pooling=true; Max Pool Size = 30; Min Pool Size = 5;"

The problem: My pool is somehow filling up when nobody is using it. Values must be getting stuck in the process of reading or saving values using UPDATE. 

How to repeat:
After a few minutes of saving values every few milliseconds and loading new information, the server will suddenly freeze and will not be able to recover.

Suggested fix:
Unknown. This is way over my head.
[1 Jul 2011 2:32] Gareth Jensen 
Clarification: 
MySql Connector Version = 6.4.2 (tried mostly all)
MySql Community Server Version = 5.5.13
[1 Jul 2011 2:46] Gareth Jensen 
Nevermind. The problem was in not disposing the connection properly. 
Solved.