I used to run cron to make request every 1 min to a jsp which only
write out a line of text. I uses a HttpSessionListener to listen for
any "loading request"/startup. Even ping every 1 min the loading
request still happens. I still got 500 error due to the request CPU is
is over the limit.
On Mar 4, 10:21 am, yjun hu <[email protected]> wrote:
> Can anyone confirm that Spring MVC version 2.5.6 is working fine on
> GAE?
>
> No, the same problem is also in spring2.5
>
> there is no better way to avoid that, you can try to run cron job to make
> your application reactive .
>
> Hitting a url every 1 miute, i did this ,that's all i did.
>
>
>
> On Thu, Mar 4, 2010 at 10:16 AM, Wong <[email protected]> wrote:
>
> > This problem normally happens "In the case of loading requests,
> > though, the execution time is artificially longer due to the extra
> > application initialization required.".
>
> >http://code.google.com/appengine/kb/java.html#Do_I_Need_To_Be_Concern...
>
> > I am using Spring MVC version 3.0.0 RC1. I can't really do much to
> > reduce the "loading request" or application/framework initialization
> > time. And, since this is a hard limit, I think I can't do anything
> > other than switching to other framework or plain servlet. However, I
> > also see a lot of posts by other on "loading request" issue even in
> > plain servlet.
>
> >http://groups.google.com/group/google-appengine-java/browse_thread/th...
>
> > Can anyone confirm that Spring MVC version 2.5.6 is working fine on
> > GAE?
>
> > On Mar 4, 9:51 am, gholler <[email protected]> wrote:
> > > 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]<google-appengine-java%[email protected]>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/google-appengine-java?hl=en.
>
> --
> dream or truth
--
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.
