On 27/04/2011 16:47, David Glick wrote:
>> OperationalError: (2006, 'MySQL server has gone away')
>>
>> This is happening across at least two separate instances with separate
>> storages.
> Not sure if this is the same, but I've gotten this error with
> python-mysql in a case where the mysql connection had timed out. IIRC
> the workaround was to adjust mysql's wait_timeout parameter.
DEFINITELY not this ;-)
It appears that RelStorage is causing the disconnection under these
circumstances, no other time outs are occurring and the parameters have
been deliberately adjusted on the MySQL server prior to using RelStorage
to take this into account...
cheers,
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
ZODB-Dev mailing list - ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb-dev
