How would a single cron task really help in an environment where multitudes of app servers are involved based on demand, geography, etc? So, how will the task that just ran help someone in U.S. and simultaneously help someone in Russia on the same app? I assume they are potentially running on different app servers.
On Nov 10, 1:51 am, m seleron <[email protected]> wrote: > 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 [email protected] <[email protected]>: > > > > > > > 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 <[email protected]> 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, "[email protected]" <[email protected]> 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 <[email protected]> wrote: > > >> > > have you noticed if that solves the timeout issue? > > >> > > On Mon, Nov 9, 2009 at 5:04 AM, [email protected] <[email protected]> > >> > > 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, "[email protected]" <[email protected]> wrote: > >> > > > > thanks , i will try it > > >> > > > > On Nov 9, 10:18 am, philburk <[email protected]> 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- Hide > >> > > > > >quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
