Re: [Zope-DB] ZMySQLDA thinks that MySQL has gone away
Thanks for answers. Thanks Dieter. Then, is possible to fix db.py (from ZMySQLDA). I write to the list to give the fix's link if anybody needs it in a future: http://sourceforge.net/tracker/index.php?func=detail&aid=1558521&group_id=22307&atid=374934 ___ Zope-DB mailing list Zope-DB@zope.org http://mail.zope.org/mailman/listinfo/zope-db
Re: [Zope-DB] ZMySQLDA thinks that MySQL has gone away
Pedro León López wrote at 2007-3-26 23:56 +0200: > ... > - Module Products.ZMySQLDA.db, line 389, in _abort > >error: release unlocked lock > >Other people with the problem: >http://mail.zope.org/pipermail/zope/2005-June/159762.html >http://dev.plone.org/plone/ticket/6263 > >It will be possible fix this? When I remember right (search the mailing list archives for verification!) then there is a "ZMySQLDA" version around that fixes the problem. We are using an (age old) version that does not have the problem. -- Dieter ___ Zope-DB mailing list Zope-DB@zope.org http://mail.zope.org/mailman/listinfo/zope-db
Re: [Zope-DB] ZMySQLDA thinks that MySQL has gone away
- Original Message - From: "Pedro León López" <[EMAIL PROTECTED]> To: Sent: Monday, March 26, 2007 5:56 PM Subject: [Zope-DB] ZMySQLDA thinks that MySQL has gone away Hello, I got this error when querying MySQL 5.0.26. I use Zope 2.9.4 and ZMysqlDA 2.0.9b3 (with MySQLdb 1.2.1_p2). MySQL do not gone away. This error only happens after exactly 8 hours of database inactivity. I found some information about this error. It seems is caused because MySQL close the connection after 8 hours, this time is stored at 'wait_timeout' system variable in the MySQL server. I'm doing an application for school where isn't there activity at night. Then db.py don't know this because it feels that connection is alive. Maybe the solution is check the connection before db.query. Very easy to create a simple DTML routine which accesses MySQL; then set up a cron job to run that DTML routine every few hours. Jonathan ___ Zope-DB mailing list Zope-DB@zope.org http://mail.zope.org/mailman/listinfo/zope-db
Re: [Zope-DB] ZMySQLDA thinks that MySQL has gone away
On Mon, Mar 26, 2007, Pedro Le?n L?pez wrote: > > Hello, > > > > I got this error when querying MySQL 5.0.26. I use Zope 2.9.4 and > ZMysqlDA 2.0.9b3 (with MySQLdb 1.2.1_p2). MySQL do not gone away. > > This error only happens after exactly 8 hours of database inactivity. > I found some information about this error. > > It seems is caused because MySQL close the connection after 8 hours, > this time is stored at 'wait_timeout' system variable in the MySQL > server. > > I'm doing an application for school where isn't there activity at > night. Given that mysql (or any other database) may well be restarted as part of log rotation and cron maintenance, you may well want to not depend on continuously open connections. Bill -- INTERNET: [EMAIL PROTECTED] Bill Campbell; Celestial Software LLC URL: http://www.celestial.com/ PO Box 820; 6641 E. Mercer Way FAX:(206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676 ``During times of universal deceit, telling the truth becomes a revolutionary act.'' --George Orwell ___ Zope-DB mailing list Zope-DB@zope.org http://mail.zope.org/mailman/listinfo/zope-db
[Zope-DB] ZMySQLDA thinks that MySQL has gone away
Hello, I got this error when querying MySQL 5.0.26. I use Zope 2.9.4 and ZMysqlDA 2.0.9b3 (with MySQLdb 1.2.1_p2). MySQL do not gone away. This error only happens after exactly 8 hours of database inactivity. I found some information about this error. It seems is caused because MySQL close the connection after 8 hours, this time is stored at 'wait_timeout' system variable in the MySQL server. I'm doing an application for school where isn't there activity at night. Then db.py don't know this because it feels that connection is alive. Maybe the solution is check the connection before db.query. Something similar in Zope3-Dev: http://mail.zope.org/pipermail/zope3-dev/2005-December/017052.html The solution: http://mail.zope.org/pipermail/checkins/2006-September/004078.html Traceback (innermost last): - Module ZPublisher.Publish, line 194, in publish_module_standard - Module ZPublisher.Publish, line 157, in publish - Module Zope2.App.startup, line 243, in abort - Module transaction._manager, line 107, in abort - Module transaction._transaction, line 507, in abort - Module transaction._transaction, line 580, in abort - Module Shared.DC.ZRDB.TM, line 64, in abort - Module Products.ZMySQLDA.db, line 389, in _abort error: release unlocked lock Other people with the problem: http://mail.zope.org/pipermail/zope/2005-June/159762.html http://dev.plone.org/plone/ticket/6263 It will be possible fix this? If not, how can I do the transactions with MySQL? Maybe with sqlobject o sqlalchemy? Sorry for my English and sorry for create a new thread (*ticino at hccnet.nl *put this question on the list some days ago). Thanks in advance. Peter Lion ___ Zope-DB mailing list Zope-DB@zope.org http://mail.zope.org/mailman/listinfo/zope-db
