You can't avoid it. It's how App Engine decides to start new processes when it feels like it has to. In the future we will be able to reserve instances, that may solve the issue.
On May 5, 8:50 am, Christian Goudreau <[email protected]> wrote: > This request caused a new process to be started for your application, > and thus caused your application code to be loaded for the first time. > This request may thus take longer and use more CPU than a typical > request for your application. > > How can I avoid that message ? It wasn't even a new process... > > Christian > > -- > 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.
