On Thu, Jan 21, 2010 at 12:05:43AM -0800, grassoalvaro wrote: > mysql.config > > wait_timeout=90 > max_allowed_packet=1M > connect_timeout=300 > > I fixed my pylons configurations set pool_size to 60 but didn't help. > Application is very simple, just 2 controllers, nothing complicated > (this app .I have many others with the same problem. Currently i'm > using cron to sending one GET request on every minute but this is > ugly).
In cases where I've run into this, I've turned the pool_recycle time way down - mine is set to 30, and this fixed the issue. Note that this is a workaround for another problem - in my case, I happen to know that there is a firewall that prevents long-lived TCP sessions from sitting idle. This causes pooled connections to "go away" without notifying the application stack. In theory, the better solution would be to fix that firewall's config. In practice, reducing the pool_recycle time doesn't affect my very light database load. Ross -- Ross Vandegrift [email protected] "If the fight gets hot, the songs get hotter. If the going gets tough, the songs get tougher." --Woody Guthrie
signature.asc
Description: Digital signature
