You keep pointing to reasons you believe it isn't your code, and why we are wrong, but you aren't trying the things we point out. If your time out are at 70 seconds you are doing something wrong, it shouldn't take that long to start up. EVER.
Also you are on M/S which has its own rules. Jump in to the modern world and run on HR with the rest of us happy shiny people, rather than running on the unsupported, failed experiment that M/S is. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Cezary Wagner Sent: Tuesday, January 17, 2012 1:43 AM To: Google App Engine Subject: [google-appengine] Re: Why are several production issues related to DeadlineExceededErrors being ignored? Kenneth, The timeouts could not be 10s or 15s - since DeadlineExceededErrors occurs in my logs is about 60s - I think that 10s or 15s is myths or wrong implementation since what is sense to give 60s if it should start in 15s??? Common timeouts are: 64608ms, 70806ms, 63093ms, 64499ms, ... On Jan 17, 9:10 am, Kenneth <[email protected]> wrote: > Wow, sorry to hear that. Is it java or python? I've been on hrd now > for about a month. I have the sliders set to el cheapo mode and > haven't had any timeouts at all. > > My understanding is the startup timeout is 10 seconds. The total > request timeout is 60 seconds. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
