Environment:
Linux Suse 8.2
Zope 2.7.3
MySQL 3.23.48
mySQLpython 0.9.1
ZMySQLDA 2.0.8
We are currently using the Zope Product ZMySQLDA to establish connections with a MySQL-DB and ZSQL-Methods to perform MySQL queries.
Each time a User performs a query, our SQL-Server shows a sleeping-process that is never killed. Each new query generates another sleeeping-process, even if it's via the same ZSQL-Method.
Is this behaviour inherent to the ZMySQLDA Product?
If yes, is there a way to patch the product and terminate a connection automatically after a query?
thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As I understand Zope DA machinery, you should end up with one connection per Zope thread.
If you want to try something different, get MySQLdb-1.1.10 (will be released as 1.2.0 this evening with one small fix) and ZMySQLDA-2.0.9b2. You are using ancient versions.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Environment:
Linux Suse 8.2
Zope 2.7.3
MySQL 3.23.48
mySQLpython 0.9.1
ZMySQLDA 2.0.8
We are currently using the Zope Product ZMySQLDA to establish connections with a MySQL-DB and ZSQL-Methods to perform MySQL queries.
Each time a User performs a query, our SQL-Server shows a sleeping-process that is never killed. Each new query generates another sleeeping-process, even if it's via the same ZSQL-Method.
Is this behaviour inherent to the ZMySQLDA Product?
If yes, is there a way to patch the product and terminate a connection automatically after a query?
thanks.
As I understand Zope DA machinery, you should end up with one connection per Zope thread.
If you want to try something different, get MySQLdb-1.1.10 (will be released as 1.2.0 this evening with one small fix) and ZMySQLDA-2.0.9b2. You are using ancient versions.