Connection pool weirdness
Posted: Tue 18 Jan 2005 08:56
Got a weird problem turning on connection pooling with version 2.50
After a time, i will start getting "max pool size reached" errors, even with a pool size of 100.
Looking at the database server at the time, it only had 20 open connections or so, suggesting that the connections have been closed on the server side, and the MySQL.net client not quite realizing this.
Setting a timeout value for the pool doesnt help either, nor does setting direct = false.
This is my connection string:
User=user;
Password=password;
Host=host;
Database=db;
Pooling=true;
Connection Lifetime=60;
Max Pool Size=100;
Min Pool Size=0;
Direct=true
Also, 99% of my database access is through data adapters.
After a time, i will start getting "max pool size reached" errors, even with a pool size of 100.
Looking at the database server at the time, it only had 20 open connections or so, suggesting that the connections have been closed on the server side, and the MySQL.net client not quite realizing this.
Setting a timeout value for the pool doesnt help either, nor does setting direct = false.
This is my connection string:
User=user;
Password=password;
Host=host;
Database=db;
Pooling=true;
Connection Lifetime=60;
Max Pool Size=100;
Min Pool Size=0;
Direct=true
Also, 99% of my database access is through data adapters.
