No luck!
I couldn't test number of connections. The user began complaining
updates failed.
I was forced to downgrade to 3.51.6
I had:
- Microsoft Windows 2000 prof
- MySql 4.0.18
- MyODBC 3.51.11
I needed to upgrade ODBC because in my box I installed mysql 4.1.8 for
testing. Surprisingly when I copied my mdb file with tables linked with
MyODBC 3.51.11 to production environment where 3.51.6 was in charge
something went wrong so I decided to move production to 3.51.11.
Now I have downgraded everywhere to 3.51.6 and will leave testing to
better a moment
-------- Original Message --------
Subject: Re: Number of connections have exploded with odbc 3.51.10
Date: Tue, 08 Feb 2005 08:58:42 -0800
From: Peter Harvey <pharvey [at] mysql.com>
Organization: MySQL
To: Juan Pedro Reyes Molina <jreymol [at] terra.es>
CC: Daniel Kasak <dkasak [at] nusconsulting.com.au>, myodbc [at] lists.mysql.com
References: <4207C30D.3090806 [at] terra.es>
<4207DB6D.80002 [at] nusconsulting.com.au> <42088988.3050005 [at] terra.es>
Juan Pedro Reyes Molina wrote:
> I will take a closer look at code on Thrusday, just to be sure code
> manage connections properly. Just to say that with ODBC 3.51.06 I
> didn't have such an side effect.
>
>
> Daniel Kasak wrote:
>
>> Juan Pedro Reyes Molina wrote:
>>
>>> I have an application running Microsoft Access 97 as a client an
>>> Mysql as database.
>>>
>>> Since I upgraded ODBC to 3.51.10-2 I have witnessed and unexpected
>>> grow in the number of live connection mysql server must handle.
>>> Microsoft Access seems to be openning and openning connections
>>> without closing a single one. I have been forced to set
>>> max_connection to 500 from initial 100.
>>>
>>> I have seen a single user with 338 simultaneasly open connection. I
>>> think Microsoft Access simply set aside connections without closing
>>> them and opens new ones.
>>>
>>> From user view point all works fine until mysql run short of new
>>> connections and refused to go on playing.
>>>
>>> Any help?
>>>
>> Interesting. I haven't seen this on our network. We're using Access
>> 2002, and as bad as this version is, I shudder to think what you must
>> have to deal with when administering a network of Access 97 systems.
>> Having said that, I would be surprised if this particular problem is
>> Access' fault. Are you sure you're not opening the connections
>> yourself in code? I've only ever seen Access open 1 or 2 connections
>> - and the 2nd one is ( I assume ) my code opening an ADO connection -
>> the 1st connection is used for all linked tables.
>>
>
I will be interested to knwo if this is happening in MyODBC 3.51.11 (now
on www.mysql.com).
--
Peter Harvey, Software Developer
MySQL AB, www.mysql.com
Are you MySQL certified? www.mysql.com/certification
--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc [at] m.gmane.org
