Thank you for useful information. Though various situations are thought I think that a detailed analysis might be necessary to decrease the CPU TIME.
thunks 2009/11/10 zhiw...@gmail.com <zhiw...@gmail.com>: > > now i set the schedule time to 3min, it seems work, every time i > access my app, i can hardly feel slow. my cron job access a servlet > that do nothing and just for active my app. set the schedule time to > 1min is better i think,although it will take some cpu time. > > On Nov 9, 11:31 pm, m seleron <seler...@gmail.com> wrote: >> I'm sorry very much. >> >> It examined. >> ServletContextListener#contextDestoryed was not called. >> It was necessary to examine it accurately. >> >> Nichole. >> Thank you for advice. >> >> Does not the page access speed become early? >> >> When you access that I think access speed is open in since the second >> times always >> because by the thing that keeps being accessed with cron >> >> If the display speed is still slow, the cause might be different. >> >> thanks, >> >> On Nov 9, 11:30 pm, "zhiw...@gmail.com" <zhiw...@gmail.com> wrote: >> >> >> >> > i set the time to 5min , but i can still find the contextInitialized >> > info, seems gae's time-out is very short, now i test set it to 3min >> >> > On Nov 9, 10:18 pm, Joseph Stano <joseph.st...@gmail.com> wrote: >> >> > > have you noticed if that solves the timeout issue? >> >> > > On Mon, Nov 9, 2009 at 5:04 AM, zhiw...@gmail.com <zhiw...@gmail.com> >> > > wrote: >> >> > > > it seems only contextInitialized method can be executed, and >> > > > contextDestroyed never be executed. so i can not get the time my app >> > > > alive after it was actived. i have use cron job to access a servlet >> > > > in my app every 10min to avoid app be inactive, if necessary i will >> > > > turn the time to 5min or less >> >> > > > On Nov 9, 11:40 am, "zhiw...@gmail.com" <zhiw...@gmail.com> wrote: >> > > > > thanks , i will try it >> >> > > > > On Nov 9, 10:18 am, philburk <p...@softsynth.com> wrote: >> >> > > > > > > The logging/query idea is probably the best workaround, but I >> > > > > > > don't >> > > > have >> > > > > > > such a client to do this querying. If I did, I'd just host my >> > > > > > > app on >> > > > it :) >> >> > > > > > You could schedule a cron job in GAE that tickled your app. If it >> > > > > > ran >> > > > > > often enough it might keep it resident. >> >> > > > > >http://code.google.com/appengine/docs/java/config/cron.html > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
