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
On Mar 27, 2014, at 10:03 AM, Tim Tisdall tisd...@gmail.com wrote:
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
Ah, yeah, that seems like a reasonable way of handling it.
I just don't get why I'm getting those exceptions, though, as I have it set
to recycle pool connections every 4 hrs where the mysql setting is to
expire connections after 8hrs. As far as I understand it, I shouldn't be
getting messages
what this looks like is that the connection is closed by the server due to the
MySQL timeout, then SQLAlchemy's pool, when accessed, goes to recycle those
connections, and does a close() on the existing one. Since they've been closed
server side, the close() method raises. The pool
