No, the 30 second limit is a hard limit. If a request can't finish in 30 seconds (or somewhat earlier), you get an exception. You then have an undetermined amount of time before the app engine kills your request and returns a 500 status code. You wouldn't happen to be using Spring, would you?
On Mar 3, 7:57 pm, Wong <[email protected]> wrote: > Hi, > > I am using Spring MVC. The application being cycled out overly > aggressively (sometimes less than 1 min) > > http://groups.google.com/group/google-appengine-java/browse_thread/th... > > I register an HttpSessionListener to listen for "loading request" > which takes more than 20 seconds. > > Due to the long loading request/cold start time, some requests hit the > following HardDeadlineExceededError exception. > > Log seen in my Admin Console: > com.google.apphosting.runtime.HardDeadlineExceededError: This request > (eb11499c97029f78) started at 2010/03/03 16:41:08.062 UTC and was > still executing at 2010/03/03 16:41:37.260 UTC. > > This request used a high amount of CPU, and was roughly 1.5 times over > the average request CPU limit. High CPU requests have a small quota, > and if you exceed this quota, your app will be temporarily disabled. > > I am currently on free quota. If I enable billing and set to higher > CPU quota, will I be able to avoid the HardDeadlineExceededError > problem? -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-java?hl=en.
