Hey Tin, Several people were using GAE's built in timing mechanism to ping the server to accomplish the same thing. Google came out and officially discouraged this as it tends to throw off any attempts they are currently making to fix the problem. I can't tell people what to do, but I opted to stop using this hack in the hopes that they will solve the problem.
Besides, you'll notice that this hack doesn't really work over the long run. It will essentially restart your server every minute and won't really prevent the loading request from falling on your users instead of on your ping. Jake On Jun 8, 1:54 pm, Tin <[email protected]> wrote: > Hi all: > > We have found a temporary solution for this issue: > Try with an AJAX timer kicking the server (doing nothing), maybe one > request per minute (or less) and GAE will keep our site / users in the > same node. > In our testing it could avoid the GAE web instance reloaded, but if > the request interval is long, it would cause another Datastore > performance issue:http://goo.gl/98zkthat will be fixed in near > future. > > More info please refer to here:http://goo.gl/mzQR -- 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.
