[appengine-java] Re: why my app on GAE first access is so slow

2009-11-09 Thread Joseph Stano
have you noticed if that solves the timeout issue?

On Mon, Nov 9, 2009 at 5:04 AM, 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"  wrote:
> > thanks , i will try it
> >
> > On Nov 9, 10:18 am, philburk  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
-~--~~~~--~~--~--~---



[appengine-java] Re: why my app on GAE first access is so slow

2009-11-08 Thread Joseph Stano
I'm not expecting my app to pull in much traffic, but even if it does, I
can't rely on regular visitors to keep it from timing out.

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 :)


On Sun, Nov 8, 2009 at 6:11 AM, Nichole  wrote:

>
> 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"  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 too slow
> >
> > On Nov 8, 7:00 am, Joseph Stano  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  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
-~--~~~~--~~--~--~---



[appengine-java] Re: why my app on GAE first access is so slow

2009-11-07 Thread Joseph Stano

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  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
-~--~~~~--~~--~--~---