[Zope3-Users] MySQL connection timeout problem

[Michael Bernstein]

I am running into a problem that seems superficially similar to the one
described here:
http://mail.zope.org/pipermail/zope3-dev/2005-December/thread.html#17052

Was a fix for the problem described in the above thread ever checked in?

Here is my traceback (a Zope restart also makes this go away):

Traceback (most recent call last):
  File
"/home2/webmaven2/Zope-3.2.1.source/build/lib.linux-i686-2.4/transaction/_transaction.py", line 507, in abort
    rm.abort(self)
  File
"/home2/webmaven2/Zope-3.2.1.source/build/lib.linux-i686-2.4/transaction/_transaction.py", line 634, in abort
    self._datamanager.abort(transaction)
  File
"/home2/webmaven2/Zope-3.2.1.source/build/lib.linux-i686-2.4/zope/app/rdb/__init__.py", line 445, in abort
    self._dbconn.rollback()
  File
"/home2/webmaven2/Zope-3.2.1.source/build/lib.linux-i686-2.4/zope/app/rdb/__init__.py", line 391, in rollback
    self.conn.rollback()
OperationalError: (2006, 'MySQL server has gone away')
Traceback (most recent call last):
  File "/usr/local/lib/python2.4/threading.py", line 422, in run
    self.__target(*self.__args, **self.__kwargs)
  File
"/home2/webmaven2/Zope-3.2.1.source/build/lib.linux-i686-2.4/twisted/python/threadpool.py", line 149, in _worker
    context.call(ctx, function, *args, **kwargs)
  File
"/home2/webmaven2/Zope-3.2.1.source/build/lib.linux-i686-2.4/twisted/python/context.py", line 59, in callWithContext
    return self.currentContext().callWithContext(ctx, func, *args, **kw)
  File
"/home2/webmaven2/Zope-3.2.1.source/build/lib.linux-i686-2.4/twisted/python/context.py", line 37, in callWithContext
    return func(*args,**kw)
--- <exception caught here> ---
  File
"/home2/webmaven2/Zope-3.2.1.source/build/lib.linux-i686-2.4/twisted/web2/wsgi.py", line 139, in run
    result = self.application(self.environment, self.startWSGIResponse)
  File
"/home2/webmaven2/Zope-3.2.1.source/build/lib.linux-i686-2.4/zope/app/wsgi/__init__.py", line 54, in __call__
    request = publish(request, handle_errors=handle_errors)
  File
"/home2/webmaven2/Zope-3.2.1.source/build/lib.linux-i686-2.4/zope/publisher/publish.py", line 146, in publish
    publication.handleException(
  File
"/home2/webmaven2/Zope-3.2.1.source/build/lib.linux-i686-2.4/zope/app/publication/zopepublication.py", line 243, in handleException
    transaction.abort()
  File
"/home2/webmaven2/Zope-3.2.1.source/build/lib.linux-i686-2.4/transaction/_manager.py", line 107, in abort
    return self.get().abort(sub, deprecation_wng=False)
  File
"/home2/webmaven2/Zope-3.2.1.source/build/lib.linux-i686-2.4/transaction/_transaction.py", line 507, in abort
    rm.abort(self)
  File
"/home2/webmaven2/Zope-3.2.1.source/build/lib.linux-i686-2.4/transaction/_transaction.py", line 634, in abort
    self._datamanager.abort(transaction)
  File
"/home2/webmaven2/Zope-3.2.1.source/build/lib.linux-i686-2.4/zope/app/rdb/__init__.py", line 445, in abort
    self._dbconn.rollback()
  File
"/home2/webmaven2/Zope-3.2.1.source/build/lib.linux-i686-2.4/zope/app/rdb/__init__.py", line 391, in rollback
    self.conn.rollback()
_mysql_exceptions.OperationalError: (2006, 'MySQL server has gone away')