Connection pool weirdness

Connection pool weirdness

Postby Desperado » 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 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:

Connection Lifetime=60;
Max Pool Size=100;
Min Pool Size=0;

Also, 99% of my database access is through data adapters.
Posts: 8
Joined: Mon 08 Nov 2004 08:05
Location: Norway

Re: Connection pool weirdness

Postby Oleg » Tue 18 Jan 2005 10:34

Known problems with connection pool were fixed in MySQLDirect .NET v2.70.
Please download the last version of our product (2.70.2).
Devart Team
Posts: 264
Joined: Thu 28 Oct 2004 13:56

Postby Desperado » Tue 18 Jan 2005 10:36

Thanks, i will give it a try :)
Posts: 8
Joined: Mon 08 Nov 2004 08:05
Location: Norway


Postby gift » Wed 26 Jan 2005 09:05

I have a license for 2.7.0, how can i upgrade to the new one?

Postby Devart » Thu 27 Jan 2005 14:43

You can download the last version from registered users area.
Use login information from the registration email.
Devart Team
Posts: 3174
Joined: Tue 26 Oct 2004 13:51

Return to dotConnect for MySQL