As your application becomes used more, the servlet container will not have time to time-out (will not take your servlet out of service), right?
Maybe you can log the timeouts with a servlet context listener as suggested above, and use the found average timeout to query your app from a client outside the app engine. On Nov 7, 5:32 pm, "zhiw...@gmail.com" <zhiw...@gmail.com> wrote: > yes, i think so. GAE is an exciting concept but this issue is so > bad. > if the app is an official business app, nobody can tolerate the first > time access, it is toooooooooo slow > > On Nov 8, 7:00 am, Joseph Stano <joseph.st...@gmail.com> wrote: > > > > > I have the same problem with my grails app. GAE is an exciting > > concept but this issue is so bad that I'm going to seek a different > > service to host my app. GAE+grails is too new at this point for an > > actual grails-based production site. > > > On 11/7/09, m seleron <seler...@gmail.com> wrote: > > > > Hi > > > > ServletContextListener I do know the approximate time of use. > > > > example > > > ServletContextListener#contextInitialized Been called from time to be > > > called doPost/doGet. > > > When I called to check ServletContextListener#contextDestoryed. --~--~---------~--~----~------------~-------~--~----~ 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 google-appengine-java@googlegroups.com To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~----------~----~----~----~------~----~------~--~---
