On Aug 23, 2011, at 11:21 PM, limodou wrote:
On Sat, Oct 23, 2010 at 9:22 PM, Michael Bayer mike...@zzzcomputing.com
wrote:
pool recycle means a connnection that is 3600 seconds old will be thrown
away. does not help with reconnects.
When a server gone away error is detected, the
On Wed, Aug 24, 2011 at 9:49 PM, Michael Bayer mike...@zzzcomputing.com wrote:
On Aug 23, 2011, at 11:21 PM, limodou wrote:
On Sat, Oct 23, 2010 at 9:22 PM, Michael Bayer mike...@zzzcomputing.com
wrote:
pool recycle means a connnection that is 3600 seconds old will be thrown
away. does
On Aug 24, 2011, at 10:04 AM, limodou wrote:
finally I found the problem. In my case I build my own ORM based on
sqlalchemy, I call it uliorm. And it only use base select, update,
insert, delete statements. And in order to keep the whole process can
share the same connection object, I used
On Sat, Oct 23, 2010 at 9:22 PM, Michael Bayer mike...@zzzcomputing.com wrote:
pool recycle means a connnection that is 3600 seconds old will be thrown
away. does not help with reconnects.
When a server gone away error is detected, the entire connection pool is
thrown away and rebuilt.
Hi Guys,
One of our MySQL servers crashed yesterday. After we recovered it, a
small SQLAlchemy-based app we have running against it kept throwing
'MySQL server has gone away' even though we have pool_recycle set to 3600.
Any ideas why that might be?
Curious as to why SA doesn't try and
pool recycle means a connnection that is 3600 seconds old will be thrown away.
does not help with reconnects.
When a server gone away error is detected, the entire connection pool is
thrown away and rebuilt. So assuming one engine, you'd get this error once for
each connection that is
