[Sqlalchemy-tickets] Issue #3107: MySQL server gone away (zzzeek/sqlalchemy)
Brought to you by:
zzzeek
|
From: Juda K. <iss...@bi...> - 2014-07-01 09:16:23
|
New issue 3107: MySQL server gone away https://bitbucket.org/zzzeek/sqlalchemy/issue/3107/mysql-server-gone-away Juda Kaleta: We are using SQLAlchemy to pool connections to MySQL server (together with django-mysqlpool). After upgrading to 0.9.6 many error like this have started to appear frequently. ``` sqlalchemy.pool.QueuePool Exception during reset or similar Traceback (most recent call last): File "/home/mcat/venv_sk/local/lib/python2.7/site-packages/sqlalchemy/pool.py", line 557, in _finalize_fairy fairy._reset(pool, echo) File "/home/mcat/venv_sk/local/lib/python2.7/site-packages/sqlalchemy/pool.py", line 688, in _reset pool._dialect.do_rollback(self) File "/home/mcat/venv_sk/local/lib/python2.7/site-packages/sqlalchemy/pool.py", line 79, in do_rollback dbapi_connection.rollback() OperationalError: (2006, 'MySQL server has gone away') ``` Recycle and other arguments passed to pool haven't changed and should be correct. |