In my experience, java apps are unloaded after about 50 seconds without a hit.
On Feb 17, 1:36 pm, peterk <[email protected]> wrote: > My background is python, but yes, instances of your application are > spooled down and perhaps taken out of memory altogether if the app > goes idle. So the next request to your app after this happens takes a > bit longer to be served, because an instance of your application has > to be spooled back up before it can be served. This is true in python, > and I believe I read that it may actually be more severe a problem > with Java. > > You can try and keep your app 'hot' by polling it automatically with > enough regularity, or setting up a cron job within the app to poll a > empty request handler etc. > > On Feb 17, 5:17 am, netcompetency <[email protected]> wrote: > > > > > Hi all, > > i have some labs on Google App Engine and find some "strange" yet > > "consistent" behaviour. My app is based on Spring/JPA. No error/ > > exception and working properly. The issue is with performance. > > > If we are not using the apps for some time --- for example for an hour > > --- the application is like being "hibernated". It needs time to > > response to the first request. > > > Is this the case ? Is there an documentation on this ? > > > Cheers, > > > Eko Budhi S -- 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.
