Eric, Thank you for responding. We use a database on only one of the apps, it is a Oracle 11G RAC Server. I'll get the DBA to double check the idle timeout for that DB. Though the other app does not use a database.
On Mon, Aug 4, 2014 at 2:39 PM, Eric Wong <e...@80x24.org> wrote: > Tony Devlin <tonydev...@gmail.com> wrote: > > 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 > workers > > 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 > starts > > all over again. > > This sounds like the idle timeout for MySQL (or similar) kicking in. > What database(s) or other backends are you using? > > That said, we've had problems with hibernate/suspend in the past, > so I'll double check. > -- *Tony Devlin* Founder / CTO PrintKEG.com (800) 676-0856 http://www.printkeg.com Facebook: http://www.facebook.com/printkeg Twitter: https://twitter.com/printkeg 250 business cards are only $10 http://www.printkeg.com/cheap-business-cards.php
