Actually my app is written in Groovy on Grails. It is supposed to be supported by App Engine and seems to work OK, with a few warts and this problem. Unfortunately it means I probably don't have as much control over application start up times as I might with another framework.
Is there any way to increase the amount of time my app is allowed to spend spinning up? If not, then app engine really doesn't support Groovy on Grails. We should probably note this stuff somewhere. On Mar 7, 6:08 pm, John Patterson <[email protected]> wrote: > The Jetty server is not used again after an error so another one has > to be spun-up for you next request. The only thing you can do about > it is tackle the HDEEs which is not always easy. It sounds like they > might be due to long start-up time? > > If so there are a number of tactics you can use to reduce this: > > Use lazy initialization as much as possible. > Split your app into a user facing version and an admin version that > share the same datastore > If you use Guice try using the non-AOP version that does not enhance > classes at startup > Spring - not sure but others mentioned turning off classpath scanning > Try reducing external jar dependencies - not sure how much affect > loading these has > > If the cause of the HDEEs is that your requests take a long time then > you'll need to reduce processing time > > Try using the Deferred class: > > http://groups.google.com/group/google-appengine-java/browse_thread/th... > > On 8 Mar 2010, at 05:37, Ken wrote: > > > > > I am getting HardDeadlineExceededErrors. What do you mean that the > > instance will be disposed? What can I do about it? > > > Thank you. > > > On Mar 7, 5:18 pm, John Patterson <[email protected]> wrote: > >> If there are errors like HardDeadlineExceededError then the server > >> instance will be disposed. Could this be the problem? > > >> On 8 Mar 2010, at 05:09, Ken wrote: > > >>> I was just looking in the logs after making numerous requests to my > >>> application. Something is seriously wrong. I'm even having high > >>> CPU > >>> on static files. In one request it took 45 seconds of CPU to return > >>> the favicon.ico file. I guess this is really related to starting a > >>> server instance, but if that's true then the server is going down > >>> after only a few seconds of use. It is starting the server > >>> handling a > >>> request and a few seconds later dropping the server. It isn't even > >>> staying up a minute. > > >>> On Mar 7, 3:13 pm, Ken <[email protected]> wrote: > >>>> I have a very simple Groovy on Grails application installed that > >>>> uses > >>>> only a single table. The application is really just the scaffolded > >>>> edits on this table with very few modifications to make it work. > >>>> So > >>>> it doesn't really do anything. > > >>>> About one in five clicks result in an error. The exception is a > >>>> Hard > >>>> Deadline Exceeded and there is a warning about the CPU limit as > >>>> well. > >>>> Randomly a request will take around 30 seconds of CPU for no > >>>> reason. > >>>> There is no change in the code. There is no change to the data. > >>>> The > >>>> exact same request will return with essentially no latency and then > >>>> it > >>>> will take 30 seconds of CPU. > > >>>> I thought this might be some kind of weirdness with Grails, but > >>>> there > >>>> are several issues listed that seem to be related to same issue: > > >>>>http://code.google.com/p/googleappengine/issues/detail?id=2621http:// > >>>> ... > >>>> ?id=2840http://code.google.com/p/googleappengine/issues/detail?id=2691http:// > >>>> ... > >>>> ?id=2837http://code.google.com/p/googleappengine/issues/detail?id=2846 > > >>>> I've stared them all because they all are likely related to the > >>>> same > >>>> problem I'm having. > > >>>> I was hoping that someone here knew what was going on and might be > >>>> able to help me resolve it. In one of the messages above someone > >>>> mentions moving an application to another "shard" to solve the > >>>> problem. What does this mean? Is it really a potential solution? > > >>>> Thank you. > > >>> -- > >>> 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 > >>> athttp://groups.google.com/group/google-appengine-java?hl=en > >>> . > > > -- > > 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 > > athttp://groups.google.com/group/google-appengine-java?hl=en > > . -- 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.
