Hey Thomas, I get it all the time - to the point where all of my demonstration applications are using the development server hosted on a non-GAE machine :) Anyways, Ikai is (was) aware of the issue from awhile back, but I'm not sure it's taking priority.
Jake On Jun 4, 1:33 am, Thomas <[email protected]> wrote: > On 6月4日, 下午12時02分, Jake <[email protected]> wrote: > > > I understand that there can be problems with everyone having a full- > > time reserved JVM. My problem is simply that the instance restarts > > too frequently. I mean, honestly, one SINGLE page request results in > > TWO application restarts? Even if you get it down to 4 seconds, > > that's 8-10 seconds just for the page to load. > > I personally have never seen the two continuous app loading in a > single request before. Maybe you should open an issue to let google > guy's help you. > > > I confess, I'm not an expert on the technology involved. Is it > > technologically difficult to say, if a JVM gets any traffic, hold it > > open for 5 minutes at a minimum. This can be cheated by the "keep > > alive" pinging that people are doing, but perhaps that can be ignored > > and only external traffic counts? > > I guess google can't tell the 'keep alive' tasks from normal tasks > without reverse engineering the code. Banning 'keep alive' task will > kill the normal tasks also probably. -- 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.
