Today I found the following traceback in my logs:
2014-03-27 13:55:59,876 ERROR [sqlalchemy.pool.QueuePool _close_connection
b'uWSGIWorker2Core14'] Exception closing connection <oursql.Connection
object at 0x7fecfdf6a140>
Traceback (most recent call last):
File
"/sites/ColanderAlchemy/SQLAlchemy-0.9.3-py3.3-linux-x86_64.egg/sqlalchemy/pool.py",
line 243, in _close_connection
self._dialect.do_close(connection)
File
"/sites/ColanderAlchemy/SQLAlchemy-0.9.3-py3.3-linux-x86_64.egg/sqlalchemy/engine/default.py",
line 401, in do_close
dbapi_connection.close()
File "connection.pyx", line 193, in oursql.Connection.close
(oursqlx/oursql.c:6143)
File "connection.pyx", line 240, in oursql.Connection.rollback
(oursqlx/oursql.c:6562)
File "connection.pyx", line 207, in oursql.Connection._raise_error
(oursqlx/oursql.c:6317)
oursql.OperationalError: (2006, 'MySQL server has gone away', None)
Shouldn't SQLAlchemy closing a connection catch this type of exception and
ignore it? If the mysql connection "has gone away", can it not be
considered "closed"?
-Tim
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.
