It could also be that your TCP keepalive interval is higher than your dat= abase server=E2=80=99s connection timeout. I=E2=80=99ve run into that in = the past. =20
On Monday, August 4, 2014 at 11:39 AM, Eric Wong wrote: > Tony Devlin <tonydevlin=40gmail.com (mailto:tonydevlin=40gmail.com)> wr= ote: > > We have an issue where if a site is not accessed for around (average)= 30 > > minutes the next query will timeout, and it will timeout on all the w= orkers > > opened. IE: If I have two workers, then both of those workers will > > timeout, even if the first one, > > after timeout, starts to work. As soon as the second worker is called= upon > > it will timeout. Then everything runs perfectly good and great until = the > > site is not accessed for 30 minutes or more. Then the timeout issue s= tarts > > all over again. > > =20 > =20 > =20 > This sounds like the idle timeout for MySQL (or similar) kicking in. > What database(s) or other backends are you using=3F > =20 > That said, we've had problems with hibernate/suspend in the past, > so I'll double check. > =20 > =20
