Re: [appengine-java] Re: Slow cold starts
That totally sucks. I can understand that it takes up more resources to have an app always loaded in an instance but when minimum instances is set, then it should mean that the app is kept in memory. If what you write is true (and I guess it is since nobody from Google has objected to it) then Google is not fulfilling what they themselves claim: Because App Engine keeps idle instances in reserve, it is unlikely that requests will enter the pending queue except in exceptionally high load spikes. http://code.google.com/appengine/docs/adminconsole/performancesettings.html On Thursday, March 8, 2012 10:10:03 PM UTC+1, Mark Rathwell wrote: Just wanted to follow up on this: Idle instances set to 1: 7 of 10 requests were loading requests (20-30 seconds) Idle instances set to 2: 3 of 9 requests were loading requests (and cost was about 4 times as much) This is a test app, with no other traffic, no new versions uploaded, etc., and these requests were about once a day for the last few weeks. I'm giving up on finding a setting that will mimic always on for low traffic apps, and just setting up a cron job to ping the apps regularly. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/ly0xBCd9rVkJ. 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: Slow cold starts
Ok, interesting. Have you tried setting minimum instances to one? On Monday, February 27, 2012 8:40:41 AM UTC+1, Tapir wrote: From my experience, an app without billing enabled will encounter many many slow cold starts. That is why although my app visits is small but I still made my app billing enabled. But today, there are suddenly many cold starts again on my app even if it is billing enabled. On Feb 27, 12:30 am, Anders blabl...@gmail.com wrote: Thanks. The app no longer has billing enabled (needed to be able to adjust minimum instances), but that could be worth trying. On Sunday, February 26, 2012 2:26:00 PM UTC+1, Mike Lawrence wrote: I noticed similar behavior. I think the auto setting for minimum number of instances changed from two to zero active instances. I changed from auto to one, and my app is much more responsive. setting minimum instances higher will co$t you more On Feb 25, 9:36 am, Anders blabl...@gmail.com wrote: In the recent weeks the cold starts for Java apps have started to take a long time in my experience. More than three seconds to load a webpage is too long generally for a high quality end user experience. I assume it happens when the physical GAE servers become too crowded resulting in sluggish cold start loading of apps from the file system (and/or maybe because of delays in the distributed file system itself). -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/gCjF8DpwWJcJ. 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.
Re: [appengine-java] Re: Slow cold starts
Hmm... Not good. Google writes that setting minimum number of instances means keeping them in reserve so that cold starts will be unlikely unless there are exceptionally high load spikes. Sounds like a bug in GAE then if your application is set to minimum one instance and you still get many cold starts. Plus to Google: Seems like my email address is sometimes published because I usually get zero spam mail in my Gmail account except when I have recently posted something in a Google Group like this. So spammers seem to be able to somehow get my email address by scraping information from Google Groups or via some subscription mechanism. Very bad indeed if true (with the disclaimer that maybe it's not Google that is leaking email addresses). On Wednesday, February 29, 2012 7:24:45 PM UTC+1, Mark Rathwell wrote: Ok, interesting. Have you tried setting minimum instances to one? I have an app I've been testing, with billing enabled and minimum instances set to one. I check the app 1 - 2 times per day, and the overwhelming majority of those requests are cold starts. I just set the minimum instances to 2, so I'll see how it responds over the next few days. On Wed, Feb 29, 2012 at 6:25 AM, Anders wrote: Ok, interesting. Have you tried setting minimum instances to one? On Monday, February 27, 2012 8:40:41 AM UTC+1, Tapir wrote: From my experience, an app without billing enabled will encounter many many slow cold starts. That is why although my app visits is small but I still made my app billing enabled. But today, there are suddenly many cold starts again on my app even if it is billing enabled. On Feb 27, 12:30 am, Anders wrote: Thanks. The app no longer has billing enabled (needed to be able to adjust minimum instances), but that could be worth trying. On Sunday, February 26, 2012 2:26:00 PM UTC+1, Mike Lawrence wrote: I noticed similar behavior. I think the auto setting for minimum number of instances changed from two to zero active instances. I changed from auto to one, and my app is much more responsive. setting minimum instances higher will co$t you more On Feb 25, 9:36 am, Anders wrote: In the recent weeks the cold starts for Java apps have started to take a long time in my experience. More than three seconds to load a webpage is too long generally for a high quality end user experience. I assume it happens when the physical GAE servers become too crowded resulting in sluggish cold start loading of apps from the file system (and/or maybe because of delays in the distributed file system itself). -- -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/GZ1p0GyAe6MJ. 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.
Re: [appengine-java] Re: Slow cold starts
I see now that my email address indeed is visible. How is that possible?! Has Google not been able to fix such a serious privacy leak yet?!!! -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/NjhNGFhzc60J. 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: Slow cold starts
Thanks. The app no longer has billing enabled (needed to be able to adjust minimum instances), but that could be worth trying. On Sunday, February 26, 2012 2:26:00 PM UTC+1, Mike Lawrence wrote: I noticed similar behavior. I think the auto setting for minimum number of instances changed from two to zero active instances. I changed from auto to one, and my app is much more responsive. setting minimum instances higher will co$t you more On Feb 25, 9:36 am, Anders blabl...@gmail.com wrote: In the recent weeks the cold starts for Java apps have started to take a long time in my experience. More than three seconds to load a webpage is too long generally for a high quality end user experience. I assume it happens when the physical GAE servers become too crowded resulting in sluggish cold start loading of apps from the file system (and/or maybe because of delays in the distributed file system itself). -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/7bbVZyuD5oAJ. 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] Slow cold starts
In the recent weeks the cold starts for Java apps have started to take a long time in my experience. More than three seconds to load a webpage is too long generally for a high quality end user experience. I assume it happens when the physical GAE servers become too crowded resulting in sluggish cold start loading of apps from the file system (and/or maybe because of delays in the distributed file system itself). -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/b7eaYKqwRP4J. 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] Compiled jsp file: FileNotFoundException
This is clearly a GAE bug, because the file is there in other instances/requests. From the log: java.lang.RuntimeException: java.io.FileNotFoundException: /base/data/home/apps/s~tweetvote2/1.353082386135622494/_ah/java_compiled/WEB-INF/classes/org/apache/jsp/about_jsp.class -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/Jq4ELxgA7eoJ. 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] threadsafe and sessions-enabled
If an application has both threadsafe and sessions-enabled set to true, then will calls to the session API block so that one frontend instance can only execute one such call at a time when there are several threads running? -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/DrIxHS90BRwJ. 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.
Re: [giannim] [appengine-java] threadsafe and sessions-enabled
Ok, good. Thanks. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/9BHMnXPUZJkJ. 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.
Re: [giannim] [appengine-java] threadsafe and sessions-enabled
And threadsafe in this case means that the Session API can handle several calls to it simultaneously from the same frontend instance? Or will it block so that only one thread at a time can access the Session API? Because if it blocks then it will become a bottleneck since the threads then have to wait on each other when many requests are served simultaneously by one frontend instance. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/Wne2t7IdLeEJ. 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: Session/Cookie problem with redirect
I checked the response headers (in Google Chrome). When the redirect fails, then no cookie is set in the response header. Curious how this only happens sometimes. The sign in is a redirect from another redirect. First the sign in goes to a Twitter OAuth sign in page, then it's redirected back to the application and then the application makes a redirect to original page. When the sign in fails, not only is the cookie not set, the GAE session attribute is not set either when the redirect fails. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/WTF9e1KV98QJ. 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: Session/Cookie problem with redirect
Hmm... It seems that an OAuth call to a third party API sometimes throws a null pointer exception. Looks like a tricky bug, but probably not something that has to do with GAE (except if there is some server clock sync issue or something like that). -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/oonyRNGtaxwJ. 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: Session/Cookie problem with redirect
I think I have solved it now. The application passed an object from a third party library in a GAE session attribute. Sometimes when the object was retrieved from the session attribute it didn't work (often it worked but not always)! Now the application creates a new instance instead of passing it in a session attribute and so far it's working all the time. Something to do with the serialization/deserialization of the object put into the session perhaps, or that using an old instance sometimes failed and that a new instance is needed in this case. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/h2EyKyGTzWEJ. 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: Session/Cookie problem with redirect
I found something. Maybe not significant but could be. I saw in the log that two of the last sign ins that failed had a call to /_ah/warmup just prior to them. With the log text: 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. Could the warmup call mess up the cookie and session values? Seems a bit unlikely but anyway. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/Uxb5q76jK4gJ. 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: Session/Cookie problem with redirect
The object put into the session is serializable. The production server will throw an exception if the session is attempted to be set with a non-serializable object. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/Wl6DhNA92pUJ. 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: Session/Cookie problem with redirect
I haven't checked the http headers yet. The tricky thing is that it usually works fine even on the production server! It could be that I set the cookie in a non-standard way, but the session attribute is that a cookie too (I don't know fully how GAE manages sessions)? On Sunday, August 28, 2011 3:46:10 PM UTC+2, Mike Lawrence wrote: have you tried viewing the http headers in each request using chrome, firebug, httpwatch, etc? sunshine is the best disinfectant I dont think redirects normally can set cookies maybe the prod server is striping your invalid host headers on a redirect On Aug 28, 7:32 am, Simon Knott knott...@gmail.com wrote: You're not placing anything in your session which isn't serializable are you? Given that everything seems to be failing when it's starting up a new instance, which is when it will attempt to read the session out of the datastore/memcache, it may be that it can't deserialize your data. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/Mpn_VNZhhUAJ. 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: Session/Cookie problem with redirect
I noticed that when the sign in doesn't work the redirect goes to / the root. I have looked and looked for where this can happen in the code, but there is no place where the redirect can be / (unless I have missed finding it in the code). Can the sendRedirect() sometimes cause a redirect to / if something fails? Or can there be old versions of the application running in some instances (I doubt that)? -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/CrIC8SWo2tsJ. 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] Session/Cookie problem with redirect
When signing in a user I set a session attribute and a cookie and then make a sendRedirect to the destination page for the sign in. This works fine, except sometimes it doesn't work in the production server. Sometimes neither the session attribute nor the cookie is set. It always works in on the developer server (at least for all the numerous times this has been tested). -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/d-mgM5teO3EJ. 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: Session/Cookie problem with redirect
An additional detail is that I think the problem only appears after I recently have done a sign out. In the sign out the cookie age value is set to zero and the session attribute removed and then the session is invalidated (so the removal of the session attribute is redundant code but anyway just in case the implementation of the session invalidation doesn't remove it). -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/23Qs_CmkrdIJ. 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: Always On not working properly
Also, if I remember correctly, in the new pricing model there will not be possible to reserve instances other than to cut down the cost; there is no guarantee that the instances will always be loaded. So for an application with low traffic, even with operational support and several reserved frontend instances, there will still be a lot of instance swapping and sluggish page loads, because in the new pricing model a reserved frontend only means a cheaper price, not that the reserved instances will be kept warm (loaded in physical memory and running). If Google keeps having too few physical servers for the number of applications (as I estimated in a previous post), then there will always be a lot of instance swapping even with the best of instance swapping algorithms, leading to poor performance and an amateurish/low-end cloud computing platform. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/ro2HG8VBLzYJ. 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: Always On not working properly
And why so complicated price model? Isn't it possible to normalize difference things like CPU, number of instances, data storage and bandwidth cost etc into a single metric? And then have enough physical servers etc so that too much instance swapping is prevented. With a normalization like that it would be as simple as paying for electricity. The amount of resources an application needs, regardless of whether it's more CPU or data storage or bandwidth or primary memory or whatever, since the resources are normalized they can all be combined into a single parameter, would be like paying for the amount of electricity used. Too much optimization by having all kinds of parameters for customers to choose between and alter will likely be a suboptimization overall. Some customers may need to fine-tune things on a detailed level, so manual options could be available but also an automatic default price model that would be as simple as paying for electricity. I don't want to regulate the budget manually except for setting a monthly amount. And instead have an algorithm automatically distributing the budget amount for the different kinds of resources. And have statistics presented showing how much the application consumes for each resource type such as CPU, data storage etc, so that I can optimize the application without having to manually adjust the budget distribution. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/Sp8E-UQ8QyQJ. 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: Always On not working properly
I use the high replication datastore if that's what you mean by high availability. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/dLmzCylzGN4J. 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: Always On not working properly
Another problem when switching to Always On is that sometimes when I upload new versions of the application no change happens! Even when I wait several minutes after the upload. Is Google App Engine really a finished product? Or is it still in a trial version? It's starting to feel really shaky. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/eTV3xUELa64J. 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: Always On not working properly
In this case it was the Java code. First it it took me several uploads to make the change happen. Now it's not even working with several uploads. I have used appcfg rollback recently and will try that again if I can get the upload to work. Frustrating! -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/IaoFHGA7jnYJ. 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: Always On not working properly
Now the performance is pretty good. And to not appear as a total jerk I want to add that overall GAE is really awesome. Now I can focus on the really challenging part which is to generate massive traffic. And then it will be interesting to see how GAE will manage that. :-) -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/r6ZbFNcv-fsJ. 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: Always On not working properly
Hi Jose, Ok, setting idle instances would be similar to Always On I assume. Plus I read in one of those threads that they are working on fixing some instance scheduler bug. So that should make the performance smoother. Unless they try to squeeze too many instances into too few physical servers. Because then even an idle instance can become very sluggish. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/HW3Anafooa8J. 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] Always On not working properly
I switched on the Always On option and it works inasmuch as the dashboard shows three resident instances but new instances are started sometimes with only a few seconds between page accesses with very low overall traffic. In the log the message 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. pops every 10 log lines or so. Surely, with Always On activated, new instances should not be started several times every minute?! The reason I switched it on was to prevent exactly that from happening. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/zVryoH1Q_6QJ. 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: Always On not working properly
https://lh3.googleusercontent.com/-HJJBk5I6WUI/TlZvPKlYK_I/ACM/i4WYsSQLoiA/sc.png Now it's starting to get even worse than before Always On was activated! See above picture (with a lot of red in it, lol). The app engine id is: tweetvote2 -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/0Erv8xtMzj4J. 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: Always On not working properly
Ok, but as Always On is working now is totally unacceptable. Google needs to fix this immediately imo. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/v4njtRVeZYUJ. 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: Always On not working properly
I'm not sure if it's worse with Always On activated or inactivated. I activated that option because new instances were starting all the time, like every second when it was really bad. So Always On is perhaps better than that, but it's really horrible either way! I'm surprised that Google hasn't fixed the problem if it has been known for some time. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/ZrRxmkx2B4MJ. 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: Always On not working properly
Isn't it possible to treat instances similar to pages in a virtual memory page swapping algorithm? And if too many page swaps are made too frequently then either the page swapping algorithm sucks or there is too little physical memory (or both :D). I doubt that the Google engineers are using a crappy instance swapping algorithm which indicates that maybe they are trying to cram too many instances into the available physical servers and that this is the reason why there is so much instance swapping going on in GAE. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/_HGZWMcIY4oJ. 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: Feelings about new pricing model
The new price model says $0.08/hour for every new instance. http://www.google.com/enterprise/appengine/appengine_pricing.html That sounds extremely expensive, or have I missed something? One GAE server no doubt runs many instances, or? 0.08 * 24 * 30 = $57.6 per month. Yikes. At the moment my apps have very low traffic, but already today 2 instances are often running. With increased traffic many instances may be running all the time resulting in huge monthly bills. On May 10, 11:18 pm, Marcel Overdijk marceloverd...@gmail.com wrote: Today Google announced the new pricing model to be effective later this year (http://googleappengine.blogspot.com/2011/05/year-ahead-for- google-app-engine.html). I always like the pay per usage model compared to the pay per instance model. Because of this change by Google, other platforms - like VMware's CloudFoundry - might be on the same pricing level and offer more advantage as they are more flexible in terms of frameworks supported. I'm wondering how other developers feel about this change in pricing model. -- 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: Feelings about new pricing model
And it is said that the new price model is more transparent. But CPU hours at least sounds more transparent. How many instances share the same CPU in a GAE server? 1, 2, 10 or 100? The new price model seems more opaque. For example, if 10 instances share the same CPU, then only (at best, not counting overhead) 1/10 of the CPU power will be available to each instance given they consume the same amount CPU time each, and yet all 10 instances will be billed the full price! What a rip off. Or probably I have missed something, but still, it's not clear. A better price model is needed imo. -- 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.
Re: [appengine-java] Re: Feelings about new pricing model
If the application is multithreaded then new instances would not be needed, but yes if it's a single thread application and new requests need to be served then I suppose new instances must be spawned if the latency becomes too large. But will that happen often in practice? -- 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.
Re: [appengine-java] Re: JSP page as Warmup Servlet
Ok. Excellent. -- 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] JSP page as Warmup Servlet
Is it possible to use a JSP page as a warmup Servlet in Google App Engine for Java? Example: servlet servlet-namesearch/servlet-name jsp-file/search.jsp/jsp-file load-on-startup1/load-on-startup /servlet Sice JSP pages are compiled into Servlets this should work in theory, unless JSP pages and ordinary Servlets are treated differently under the hood. -- 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.
Re: [appengine-java] JSP page as Warmup Servlet
Good. I thought it would be convenient to use an already existing JSP page as a warmup call. Plus, that makes it possible to ensure that the warmup call actually accesses the real logic of the application. And if/when the application changes, the warmup call will automatically reflect those changes without having to maintain a separate warmup servlet. Another thing that I'm not sure about yet is that maybe JSP pages get recompiled for every new Google App Engine instance! Then it's important to make warmup calls to all JSP pages that need to be compiled for fast first access. For example by having a separate warmup JSP page that does dynamic include of other JSP pages. Or maybe the compile if very fast nowadays. Or maybe JSP pages that are already compiled remains compiled when new Google App Engine instances are started. I have to research that. JSP dispatch from a separate warmup servlet could be a good idea. On Tue, May 17, 2011 at 12:36 AM, Ikai Lan (Google) ika...@google.comwrote: Yes. Warmup servlets are just URL for you to hit: http://code.google.com/appengine/docs/java/config/appconfig.html#Warmup_Requests http://code.google.com/appengine/docs/java/config/appconfig.html#Warmup_RequestsThat being said, why would you want to use a JSP as a warmup servlet? The code will be easier to test/maintain in a servlet itself. Worst case scenario you can always use JSP dispatch to the JSP. Ikai Lan Developer Programs Engineer, Google App Engine Blog: http://googleappengine.blogspot.com Twitter: http://twitter.com/app_engine Reddit: http://www.reddit.com/r/appengine On Sun, May 15, 2011 at 11:18 PM, Anders i...@blabline.com wrote: Is it possible to use a JSP page as a warmup Servlet in Google App Engine for Java? Example: servlet servlet-namesearch/servlet-name jsp-file/search.jsp/jsp-file load-on-startup1/load-on-startup /servlet Sice JSP pages are compiled into Servlets this should work in theory, unless JSP pages and ordinary Servlets are treated differently under the hood. -- 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. -- 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. -- 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.
Re: [appengine-java] JSP page as Warmup Servlet
But if /_ah/warmup is mapped, then the documentation says that the service() method of the mapped servlet will be called: http://code.google.com/appengine/docs/java/config/appconfig.html#Using_a_Custom_Servlet Does the service() method in the compiled JSP servlet make a call to _jspService()? Otherwise the JSP page code will not be accessed. On Tue, May 17, 2011 at 12:43 AM, Don Schwarz schwa...@google.com wrote: To be clear, load-on-startup just means the servlet will be *initialized* during the warmup request (not executed). For JSPs, this means that the jspInit() method is called. If you override it to do something expensive this may provide a big benefit, but otherwise you will just get the benefit of loading the JSP infrastructure ahead of time. If you really want to execute a JSP as a warmup request, you should declare it explicitly with a servlet using jsp-file and them map it to /_ah/warmup. On Mon, May 16, 2011 at 5:36 PM, Ikai Lan (Google) ika...@google.comwrote: Yes. Warmup servlets are just URL for you to hit: http://code.google.com/appengine/docs/java/config/appconfig.html#Warmup_Requests http://code.google.com/appengine/docs/java/config/appconfig.html#Warmup_RequestsThat being said, why would you want to use a JSP as a warmup servlet? The code will be easier to test/maintain in a servlet itself. Worst case scenario you can always use JSP dispatch to the JSP. Ikai Lan Developer Programs Engineer, Google App Engine Blog: http://googleappengine.blogspot.com Twitter: http://twitter.com/app_engine Reddit: http://www.reddit.com/r/appengine On Sun, May 15, 2011 at 11:18 PM, Anders i...@blabline.com wrote: Is it possible to use a JSP page as a warmup Servlet in Google App Engine for Java? Example: servlet servlet-namesearch/servlet-name jsp-file/search.jsp/jsp-file load-on-startup1/load-on-startup /servlet Sice JSP pages are compiled into Servlets this should work in theory, unless JSP pages and ordinary Servlets are treated differently under the hood. -- 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. -- 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. -- 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. -- 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.
Re: [appengine-java] JSP page as Warmup Servlet
Oh, only jspInit(), not jspService() that renders the actual page. Hmm... Then it's perhaps better to have a separate warmup servlet instead. Overriding the jspInit() method sounds like messy coding. Alternatively to have load-on-startup1/load-on-startup for both JSP pages and a separate warmup servlet that makes calls to the datastore etc can be used (and not map _ah_warmup so that the default warmup logic remains). -- 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: JSP page as Warmup Servlet
The documentation doesn't mention it (as far as I could see), but I take it that warmup servlets can be given admin auth-constraint. -- 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: Google maps geocoder responds with 620 error since last nights server maintenance
Any updates Ikai?
On 21 Feb, 03:46, Ivan Pardo trux...@gmail.com wrote:
I'm having the same problem.
On Feb 20, 3:06 am, Anders anders.ny...@gmail.com wrote:
Still having problems here as well. What you are seeing Jeff is
probably the bot information page, besides 620s I'm getting this
response:
htmlheadmeta http-equiv=content-type content=text/html;
charset=utf-8/titleSorry.../titlestyle body { font-family:
verdana arial sans-serif; background-color: #fff; color: #000; }/
style/headbodydivtabletrtdbfont face=times
color=#0039b6 size=10G/fontfont face=times color=#c41200
size=10o/fontfont face=times color=#f3c518 size=10o/fontfont
face=times color=#0039b6 size=10g/fontfont face=times
color=#30a72f size=10l/fontfont face=times color=#c41200
size=10e/font/b/tdtd style=text-align: left; vertical-align:
bottom; padding-bottom: 15px; width: 50%div style=border-bottom:
1px solid #dfdfdf;Sorry.../div/td/tr/table/divdiv
style=margin-left: 4em;h1We're sorry.../h1p... but your
computer or network may be sending automated queries. To protect our
users
On 20 Feb, 04:53, Jeff Schnitzer j...@infohazard.org wrote:
It doesn't seem to be working.
Not only am I still seeing a ton of 620s, but half the time I'm also
getting something that doesn't parse as JSON. It contains an
unexpected ''. I'm guessing it's some sort of error message getting
rendered in html or xml.
org.codehaus.jackson.JsonParseException: Unexpected character (''
(code 60)): expected a valid value (number, String, array, object,
'true', 'false' or 'null')
at [Source: java.io.bytearrayinputstr...@908faf; line: 1, column: 2]
When I try the same URL from my desktop, it works fine.
Jeff
On Fri, Feb 19, 2010 at 2:16 PM, Ikai L (Google) ika...@google.com
wrote:
The configuration changes have been made and should be live shortly if
not
immediately. Can you check and let me know if they are working? I'd
give it
about ~30 minutes if it doesn't work right away.
On Fri, Feb 19, 2010 at 10:56 AM, Ikai L (Google) ika...@google.com
wrote:
I think there's a version in the main group. I'll post to that one
first
if it exists.
On Fri, Feb 19, 2010 at 10:56 AM, Ikai L (Google) ika...@google.com
wrote:
Hey guys,
I just wanted to let everyone know that I'm working on this. Stay
tuned.
I'll post to this thread when I have updates.
On Fri, Feb 19, 2010 at 10:51 AM, Jeff Schnitzer j...@infohazard.org
wrote:
It helps to have some links... please star these issues!
http://code.google.com/p/googleappengine/issues/detail?id=2806
http://code.google.com/p/gmaps-api-issues/issues/detail?id=2186
This problem is a really big deal, several features of my app depend
on reverse geocodes. It looks like a simple whitelisting issue,
shouldn't be too hard to fix!
Jeff
On Fri, Feb 19, 2010 at 12:26 AM, Anders anders.ny...@gmail.com
wrote:
Same problem here. No problems for 4 months with unchanged mapping
code and as of the last day mostly 620 results.
I am running on the python appengine but as previously said this is
probably an issue with the geocoder IP limit.
On 19 Feb, 07:21, Ivan Pardo trux...@gmail.com wrote:
ive entered this is a bug on the maps api bug tracker. ive tried
on
2
google apps accounts and ive asked others to confirm. it looks
like
geocoding is impossible from google apps servers.
On Feb 18, 6:25 pm, Ivan Pardo trux...@gmail.com wrote:
At least now I can be certain that it's not a problem with my
code.
I
can only hope that Google can fix this problem ASAP, as my
application
is absolutely useless without a working geocoder.
On Feb 18, 5:44 pm, Jeff Schnitzer j...@infohazard.org wrote:
I'm also seeing 620 errors for most (possibly all) of my
reverse
geocode requests.
Jeff
--
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-j...@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.
--
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-j...@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.
--
Ikai Lan
Developer Programs Engineer, Google App Engine
http://googleappengine.blogspot.com|http
[appengine-java] Re: Google maps geocoder responds with 620 error since last nights server maintenance
It is working for me now, thanks for the help!
On 23 Feb, 00:16, Ikai L (Google) ika...@google.com wrote:
I've updated the whitelist. It should take a bit for the changes to
propagate. Let me know if it still doesn't work for you in about 45 minutes,
please send me your Geo API key.
On Mon, Feb 22, 2010 at 1:14 PM, Ikai L (Google) ika...@google.com wrote:
I'm working on it. Seems like I sent out a false all clear because this
began working for a portion of applications.
On Mon, Feb 22, 2010 at 12:43 PM, Anders anders.ny...@gmail.com wrote:
Any updates Ikai?
On 21 Feb, 03:46, Ivan Pardo trux...@gmail.com wrote:
I'm having the same problem.
On Feb 20, 3:06 am, Anders anders.ny...@gmail.com wrote:
Still having problems here as well. What you are seeing Jeff is
probably the bot information page, besides 620s I'm getting this
response:
htmlheadmeta http-equiv=content-type content=text/html;
charset=utf-8/titleSorry.../titlestyle body { font-family:
verdana arial sans-serif; background-color: #fff; color: #000; }/
style/headbodydivtabletrtdbfont face=times
color=#0039b6 size=10G/fontfont face=times color=#c41200
size=10o/fontfont face=times color=#f3c518 size=10o/fontfont
face=times color=#0039b6 size=10g/fontfont face=times
color=#30a72f size=10l/fontfont face=times color=#c41200
size=10e/font/b/tdtd style=text-align: left; vertical-align:
bottom; padding-bottom: 15px; width: 50%div style=border-bottom:
1px solid #dfdfdf;Sorry.../div/td/tr/table/divdiv
style=margin-left: 4em;h1We're sorry.../h1p... but your
computer or network may be sending automated queries. To protect our
users
On 20 Feb, 04:53, Jeff Schnitzer j...@infohazard.org wrote:
It doesn't seem to be working.
Not only am I still seeing a ton of 620s, but half the time I'm also
getting something that doesn't parse as JSON. It contains an
unexpected ''. I'm guessing it's some sort of error message
getting
rendered in html or xml.
org.codehaus.jackson.JsonParseException: Unexpected character (''
(code 60)): expected a valid value (number, String, array, object,
'true', 'false' or 'null')
at [Source: java.io.bytearrayinputstr...@908faf; line: 1, column:
2]
When I try the same URL from my desktop, it works fine.
Jeff
On Fri, Feb 19, 2010 at 2:16 PM, Ikai L (Google) ika...@google.com
wrote:
The configuration changes have been made and should be live
shortly if not
immediately. Can you check and let me know if they are working?
I'd give it
about ~30 minutes if it doesn't work right away.
On Fri, Feb 19, 2010 at 10:56 AM, Ikai L (Google)
ika...@google.com wrote:
I think there's a version in the main group. I'll post to that
one first
if it exists.
On Fri, Feb 19, 2010 at 10:56 AM, Ikai L (Google)
ika...@google.com
wrote:
Hey guys,
I just wanted to let everyone know that I'm working on this.
Stay tuned.
I'll post to this thread when I have updates.
On Fri, Feb 19, 2010 at 10:51 AM, Jeff Schnitzer
j...@infohazard.org
wrote:
It helps to have some links... please star these issues!
http://code.google.com/p/googleappengine/issues/detail?id=2806
http://code.google.com/p/gmaps-api-issues/issues/detail?id=2186
This problem is a really big deal, several features of my app
depend
on reverse geocodes. It looks like a simple whitelisting
issue,
shouldn't be too hard to fix!
Jeff
On Fri, Feb 19, 2010 at 12:26 AM, Anders
anders.ny...@gmail.com wrote:
Same problem here. No problems for 4 months with unchanged
mapping
code and as of the last day mostly 620 results.
I am running on the python appengine but as previously said
this is
probably an issue with the geocoder IP limit.
On 19 Feb, 07:21, Ivan Pardo trux...@gmail.com wrote:
ive entered this is a bug on the maps api bug tracker. ive
tried on
2
google apps accounts and ive asked others to confirm. it
looks like
geocoding is impossible from google apps servers.
On Feb 18, 6:25 pm, Ivan Pardo trux...@gmail.com wrote:
At least now I can be certain that it's not a problem with
my code.
I
can only hope that Google can fix this problem ASAP, as my
application
is absolutely useless without a working geocoder.
On Feb 18, 5:44 pm, Jeff Schnitzer j...@infohazard.org
wrote:
I'm also seeing 620 errors for most (possibly all) of my
reverse
geocode requests.
Jeff
--
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-j...@googlegroups.com.
To unsubscribe from this group, send
[appengine-java] Re: Google maps geocoder responds with 620 error since last nights server maintenance
Still having problems here as well. What you are seeing Jeff is
probably the bot information page, besides 620s I'm getting this
response:
htmlheadmeta http-equiv=content-type content=text/html;
charset=utf-8/titleSorry.../titlestyle body { font-family:
verdana arial sans-serif; background-color: #fff; color: #000; }/
style/headbodydivtabletrtdbfont face=times
color=#0039b6 size=10G/fontfont face=times color=#c41200
size=10o/fontfont face=times color=#f3c518 size=10o/fontfont
face=times color=#0039b6 size=10g/fontfont face=times
color=#30a72f size=10l/fontfont face=times color=#c41200
size=10e/font/b/tdtd style=text-align: left; vertical-align:
bottom; padding-bottom: 15px; width: 50%div style=border-bottom:
1px solid #dfdfdf;Sorry.../div/td/tr/table/divdiv
style=margin-left: 4em;h1We're sorry.../h1p... but your
computer or network may be sending automated queries. To protect our
users
On 20 Feb, 04:53, Jeff Schnitzer j...@infohazard.org wrote:
It doesn't seem to be working.
Not only am I still seeing a ton of 620s, but half the time I'm also
getting something that doesn't parse as JSON. It contains an
unexpected ''. I'm guessing it's some sort of error message getting
rendered in html or xml.
org.codehaus.jackson.JsonParseException: Unexpected character (''
(code 60)): expected a valid value (number, String, array, object,
'true', 'false' or 'null')
at [Source: java.io.bytearrayinputstr...@908faf; line: 1, column: 2]
When I try the same URL from my desktop, it works fine.
Jeff
On Fri, Feb 19, 2010 at 2:16 PM, Ikai L (Google) ika...@google.com wrote:
The configuration changes have been made and should be live shortly if not
immediately. Can you check and let me know if they are working? I'd give it
about ~30 minutes if it doesn't work right away.
On Fri, Feb 19, 2010 at 10:56 AM, Ikai L (Google) ika...@google.com wrote:
I think there's a version in the main group. I'll post to that one first
if it exists.
On Fri, Feb 19, 2010 at 10:56 AM, Ikai L (Google) ika...@google.com
wrote:
Hey guys,
I just wanted to let everyone know that I'm working on this. Stay tuned.
I'll post to this thread when I have updates.
On Fri, Feb 19, 2010 at 10:51 AM, Jeff Schnitzer j...@infohazard.org
wrote:
It helps to have some links... please star these issues!
http://code.google.com/p/googleappengine/issues/detail?id=2806
http://code.google.com/p/gmaps-api-issues/issues/detail?id=2186
This problem is a really big deal, several features of my app depend
on reverse geocodes. It looks like a simple whitelisting issue,
shouldn't be too hard to fix!
Jeff
On Fri, Feb 19, 2010 at 12:26 AM, Anders anders.ny...@gmail.com wrote:
Same problem here. No problems for 4 months with unchanged mapping
code and as of the last day mostly 620 results.
I am running on the python appengine but as previously said this is
probably an issue with the geocoder IP limit.
On 19 Feb, 07:21, Ivan Pardo trux...@gmail.com wrote:
ive entered this is a bug on the maps api bug tracker. ive tried on
2
google apps accounts and ive asked others to confirm. it looks like
geocoding is impossible from google apps servers.
On Feb 18, 6:25 pm, Ivan Pardo trux...@gmail.com wrote:
At least now I can be certain that it's not a problem with my code.
I
can only hope that Google can fix this problem ASAP, as my
application
is absolutely useless without a working geocoder.
On Feb 18, 5:44 pm, Jeff Schnitzer j...@infohazard.org wrote:
I'm also seeing 620 errors for most (possibly all) of my reverse
geocode requests.
Jeff
--
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-j...@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.
--
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-j...@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.
--
Ikai Lan
Developer Programs Engineer, Google App Engine
http://googleappengine.blogspot.com|http://twitter.com/app_engine
--
Ikai Lan
Developer Programs Engineer, Google App Engine
http://googleappengine.blogspot.com|http://twitter.com/app_engine
--
Ikai Lan
Developer Programs Engineer, Google App Engine
http://googleappengine.blogspot.com|http://twitter.com/app_engine
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group
[appengine-java] Re: Google maps geocoder responds with 620 error since last nights server maintenance
Same problem here. No problems for 4 months with unchanged mapping code and as of the last day mostly 620 results. I am running on the python appengine but as previously said this is probably an issue with the geocoder IP limit. On 19 Feb, 07:21, Ivan Pardo trux...@gmail.com wrote: ive entered this is a bug on the maps api bug tracker. ive tried on 2 google apps accounts and ive asked others to confirm. it looks like geocoding is impossible from google apps servers. On Feb 18, 6:25 pm, Ivan Pardo trux...@gmail.com wrote: At least now I can be certain that it's not a problem with my code. I can only hope that Google can fix this problem ASAP, as my application is absolutely useless without a working geocoder. On Feb 18, 5:44 pm, Jeff Schnitzer j...@infohazard.org wrote: I'm also seeing 620 errors for most (possibly all) of my reverse geocode requests. Jeff -- 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-j...@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.
