Re: [appengine-java] Re: publishing html files
Have a look at the blobstore documentation, that might help you. However I'd be inclined to mention a naughty word Amazon (ssh!) S3 might be the best way forward. On 28 February 2012 06:32, Vik vik@gmail.com wrote: Any advise on this please? Thankx and Regards Vik Founder http://www.sakshum.org http://blog.sakshum.org On Sun, Feb 26, 2012 at 11:28 AM, Vik vik@gmail.com wrote: Hie I am generated html documents using a google text doc as template (reading it using gdata apis and then doing some text manipulation). Now, I want to publish these documents somewhere so that I can refer to others giving the url of the document (which means it would be publicly accessible). Any suggestions on how do i go about it? Like where should i host these? Thankx and Regards Vik Founder http://www.sakshum.org http://blog.sakshum.org -- 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.
[appengine-java] Javaland scheduler behavior
There's been a lot of discussion of the scheduler behavior in Pythonland, but not much about it's eccentricities in Javaland. I have a threadsafe=true Java app. Let's say every request completes in exactly 1s. Settings are: idle instances min 1 max 1, latency auto/auto. Here is what I expect: * Instance1 starts up and becomes permanently resident * Instance1 serves concurrent requests up to some arbitrary CPU capcity * When Instance1 exceeds capacity: * Instance2 starts warming up * All requests remain in the pending queue for Instance1, getting processed at 1/s * concurrency * Instance2 is ready and starts processing new requests, sharing the load with Instance1 What I actually see (as far as I can determine): * Instance1 starts up and becomes permanently resident * Instance1 supports almost no concurrency. At most it's 2. (no, my app is not particularly compute intensive) * A new request comes in which for some reason can't be handled by Instance1: * Instance2 starts warming up * The new request is blocked on Instance2's pending queue, waiting 10-20s for Instance2 to be ready * In the mean time, Instance1 is actually idle * Another new request comes in and starts up Instance3 * Possibly this is while Instance2 is warming up * AFAICT, Instance1 is taking a coffee break The net result is that I have an idle website with 1 user (me) clicking around and I've already gotten multiple 20s pauses and three instances. Something is seriously wrong here. Whether or not it's rational to have so many instances started, pending requests shouldn't be shunted to non-warmed-up servers, right? I've tried upping the min latency to a high value to see if this improves the situation. If this works... shouldn't min latency *always* be as high as the startup time for an instance? I know it's been said before, but it needs to be said again... the guidance for scheduler configuration is really, really inadequate. 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-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] Javaland scheduler behavior
Five days ago I run JMeter-Tests to check the performance of my application with and without threadsafe=true. I'm in no billing mode and therefore just worked with one instance. With concurrent requests I expected a better throughput/ performance with the threadsafe=true configuration. This was not the case. The result was the same with and without the threadsafe configuration. I tested between 10 and 100 concurrent requests, but no difference at all. I seems like the threadsafe=true configuration is broken currently. Cheers Mos On Tue, Feb 28, 2012 at 5:34 PM, Jeff Schnitzer j...@infohazard.org wrote: There's been a lot of discussion of the scheduler behavior in Pythonland, but not much about it's eccentricities in Javaland. I have a threadsafe=true Java app. Let's say every request completes in exactly 1s. Settings are: idle instances min 1 max 1, latency auto/auto. Here is what I expect: * Instance1 starts up and becomes permanently resident * Instance1 serves concurrent requests up to some arbitrary CPU capcity * When Instance1 exceeds capacity: * Instance2 starts warming up * All requests remain in the pending queue for Instance1, getting processed at 1/s * concurrency * Instance2 is ready and starts processing new requests, sharing the load with Instance1 What I actually see (as far as I can determine): * Instance1 starts up and becomes permanently resident * Instance1 supports almost no concurrency. At most it's 2. (no, my app is not particularly compute intensive) * A new request comes in which for some reason can't be handled by Instance1: * Instance2 starts warming up * The new request is blocked on Instance2's pending queue, waiting 10-20s for Instance2 to be ready * In the mean time, Instance1 is actually idle * Another new request comes in and starts up Instance3 * Possibly this is while Instance2 is warming up * AFAICT, Instance1 is taking a coffee break The net result is that I have an idle website with 1 user (me) clicking around and I've already gotten multiple 20s pauses and three instances. Something is seriously wrong here. Whether or not it's rational to have so many instances started, pending requests shouldn't be shunted to non-warmed-up servers, right? I've tried upping the min latency to a high value to see if this improves the situation. If this works... shouldn't min latency *always* be as high as the startup time for an instance? I know it's been said before, but it needs to be said again... the guidance for scheduler configuration is really, really inadequate. 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-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.
[appengine-java] Re: Javaland scheduler behavior
Hi Jeff, Check this post : https://groups.google.com/forum/#!msg/google-appengine/3t5muVhXajg/SSFU-udjIhwJ Setting Idle instances to automatic, as Johan Euphrosine suggested, seems to have solved the problem, at least temporarily (I was at 1 minimum and 1 maximum before). I'm just a bit scared now to get over my daily quotas. François On Tuesday, February 28, 2012 5:34:36 PM UTC+1, Jeff Schnitzer wrote: There's been a lot of discussion of the scheduler behavior in Pythonland, but not much about it's eccentricities in Javaland. I have a threadsafe=true Java app. Let's say every request completes in exactly 1s. Settings are: idle instances min 1 max 1, latency auto/auto. Here is what I expect: * Instance1 starts up and becomes permanently resident * Instance1 serves concurrent requests up to some arbitrary CPU capcity * When Instance1 exceeds capacity: * Instance2 starts warming up * All requests remain in the pending queue for Instance1, getting processed at 1/s * concurrency * Instance2 is ready and starts processing new requests, sharing the load with Instance1 What I actually see (as far as I can determine): * Instance1 starts up and becomes permanently resident * Instance1 supports almost no concurrency. At most it's 2. (no, my app is not particularly compute intensive) * A new request comes in which for some reason can't be handled by Instance1: * Instance2 starts warming up * The new request is blocked on Instance2's pending queue, waiting 10-20s for Instance2 to be ready * In the mean time, Instance1 is actually idle * Another new request comes in and starts up Instance3 * Possibly this is while Instance2 is warming up * AFAICT, Instance1 is taking a coffee break The net result is that I have an idle website with 1 user (me) clicking around and I've already gotten multiple 20s pauses and three instances. Something is seriously wrong here. Whether or not it's rational to have so many instances started, pending requests shouldn't be shunted to non-warmed-up servers, right? I've tried upping the min latency to a high value to see if this improves the situation. If this works... shouldn't min latency *always* be as high as the startup time for an instance? I know it's been said before, but it needs to be said again... the guidance for scheduler configuration is really, really inadequate. Jeff -- 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/-/zULJyO6VtHwJ. 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: Javaland scheduler behavior
Thanks for the link. This doesn't directly address the main point I'm worried about though: * Why does any user-facing request ever sit in the pending queue for an instance that is warming-up when there is a perfectly good instance sitting there? My problem is not that GAE is spinning up new instances. My problem is that users are waiting for it. There's an instance sitting there with a low wait time in the pending queue - why is GAE shunting new requests to instances with an effective 10-20s wait time instead? Jeff On Tue, Feb 28, 2012 at 12:00 PM, Francois Masurel f.masu...@gmail.comwrote: Hi Jeff, Check this post : https://groups.google.com/forum/#!msg/google-appengine/3t5muVhXajg/SSFU-udjIhwJ Setting Idle instances to automatic, as Johan Euphrosine suggested, seems to have solved the problem, at least temporarily (I was at 1 minimum and 1 maximum before). I'm just a bit scared now to get over my daily quotas. François On Tuesday, February 28, 2012 5:34:36 PM UTC+1, Jeff Schnitzer wrote: There's been a lot of discussion of the scheduler behavior in Pythonland, but not much about it's eccentricities in Javaland. I have a threadsafe=true Java app. Let's say every request completes in exactly 1s. Settings are: idle instances min 1 max 1, latency auto/auto. Here is what I expect: * Instance1 starts up and becomes permanently resident * Instance1 serves concurrent requests up to some arbitrary CPU capcity * When Instance1 exceeds capacity: * Instance2 starts warming up * All requests remain in the pending queue for Instance1, getting processed at 1/s * concurrency * Instance2 is ready and starts processing new requests, sharing the load with Instance1 What I actually see (as far as I can determine): * Instance1 starts up and becomes permanently resident * Instance1 supports almost no concurrency. At most it's 2. (no, my app is not particularly compute intensive) * A new request comes in which for some reason can't be handled by Instance1: * Instance2 starts warming up * The new request is blocked on Instance2's pending queue, waiting 10-20s for Instance2 to be ready * In the mean time, Instance1 is actually idle * Another new request comes in and starts up Instance3 * Possibly this is while Instance2 is warming up * AFAICT, Instance1 is taking a coffee break The net result is that I have an idle website with 1 user (me) clicking around and I've already gotten multiple 20s pauses and three instances. Something is seriously wrong here. Whether or not it's rational to have so many instances started, pending requests shouldn't be shunted to non-warmed-up servers, right? I've tried upping the min latency to a high value to see if this improves the situation. If this works... shouldn't min latency *always* be as high as the startup time for an instance? I know it's been said before, but it needs to be said again... the guidance for scheduler configuration is really, really inadequate. Jeff -- 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/-/zULJyO6VtHwJ. 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] Re: Javaland scheduler behavior
Yep noticed that too since a few days. But no good explanations for the moment. François On Tue, Feb 28, 2012 at 18:25, Jeff Schnitzer j...@infohazard.org wrote: Thanks for the link. This doesn't directly address the main point I'm worried about though: * Why does any user-facing request ever sit in the pending queue for an instance that is warming-up when there is a perfectly good instance sitting there? My problem is not that GAE is spinning up new instances. My problem is that users are waiting for it. There's an instance sitting there with a low wait time in the pending queue - why is GAE shunting new requests to instances with an effective 10-20s wait time instead? Jeff On Tue, Feb 28, 2012 at 12:00 PM, Francois Masurel f.masu...@gmail.comwrote: Hi Jeff, Check this post : https://groups.google.com/forum/#!msg/google-appengine/3t5muVhXajg/SSFU-udjIhwJ Setting Idle instances to automatic, as Johan Euphrosine suggested, seems to have solved the problem, at least temporarily (I was at 1 minimum and 1 maximum before). I'm just a bit scared now to get over my daily quotas. François On Tuesday, February 28, 2012 5:34:36 PM UTC+1, Jeff Schnitzer wrote: There's been a lot of discussion of the scheduler behavior in Pythonland, but not much about it's eccentricities in Javaland. I have a threadsafe=true Java app. Let's say every request completes in exactly 1s. Settings are: idle instances min 1 max 1, latency auto/auto. Here is what I expect: * Instance1 starts up and becomes permanently resident * Instance1 serves concurrent requests up to some arbitrary CPU capcity * When Instance1 exceeds capacity: * Instance2 starts warming up * All requests remain in the pending queue for Instance1, getting processed at 1/s * concurrency * Instance2 is ready and starts processing new requests, sharing the load with Instance1 What I actually see (as far as I can determine): * Instance1 starts up and becomes permanently resident * Instance1 supports almost no concurrency. At most it's 2. (no, my app is not particularly compute intensive) * A new request comes in which for some reason can't be handled by Instance1: * Instance2 starts warming up * The new request is blocked on Instance2's pending queue, waiting 10-20s for Instance2 to be ready * In the mean time, Instance1 is actually idle * Another new request comes in and starts up Instance3 * Possibly this is while Instance2 is warming up * AFAICT, Instance1 is taking a coffee break The net result is that I have an idle website with 1 user (me) clicking around and I've already gotten multiple 20s pauses and three instances. Something is seriously wrong here. Whether or not it's rational to have so many instances started, pending requests shouldn't be shunted to non-warmed-up servers, right? I've tried upping the min latency to a high value to see if this improves the situation. If this works... shouldn't min latency *always* be as high as the startup time for an instance? I know it's been said before, but it needs to be said again... the guidance for scheduler configuration is really, really inadequate. Jeff -- 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/-/zULJyO6VtHwJ. 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] Re: Javaland scheduler behavior
I just realized I sent this to the wrong (java-specific, deprecated) Google Group. For those of you on both the google-appengine list and this one, I apologize in advance for the duplicate thread I'm about to start :-( Jeff On Tue, Feb 28, 2012 at 12:25 PM, Jeff Schnitzer j...@infohazard.orgwrote: Thanks for the link. This doesn't directly address the main point I'm worried about though: * Why does any user-facing request ever sit in the pending queue for an instance that is warming-up when there is a perfectly good instance sitting there? My problem is not that GAE is spinning up new instances. My problem is that users are waiting for it. There's an instance sitting there with a low wait time in the pending queue - why is GAE shunting new requests to instances with an effective 10-20s wait time instead? Jeff On Tue, Feb 28, 2012 at 12:00 PM, Francois Masurel f.masu...@gmail.comwrote: Hi Jeff, Check this post : https://groups.google.com/forum/#!msg/google-appengine/3t5muVhXajg/SSFU-udjIhwJ Setting Idle instances to automatic, as Johan Euphrosine suggested, seems to have solved the problem, at least temporarily (I was at 1 minimum and 1 maximum before). I'm just a bit scared now to get over my daily quotas. François On Tuesday, February 28, 2012 5:34:36 PM UTC+1, Jeff Schnitzer wrote: There's been a lot of discussion of the scheduler behavior in Pythonland, but not much about it's eccentricities in Javaland. I have a threadsafe=true Java app. Let's say every request completes in exactly 1s. Settings are: idle instances min 1 max 1, latency auto/auto. Here is what I expect: * Instance1 starts up and becomes permanently resident * Instance1 serves concurrent requests up to some arbitrary CPU capcity * When Instance1 exceeds capacity: * Instance2 starts warming up * All requests remain in the pending queue for Instance1, getting processed at 1/s * concurrency * Instance2 is ready and starts processing new requests, sharing the load with Instance1 What I actually see (as far as I can determine): * Instance1 starts up and becomes permanently resident * Instance1 supports almost no concurrency. At most it's 2. (no, my app is not particularly compute intensive) * A new request comes in which for some reason can't be handled by Instance1: * Instance2 starts warming up * The new request is blocked on Instance2's pending queue, waiting 10-20s for Instance2 to be ready * In the mean time, Instance1 is actually idle * Another new request comes in and starts up Instance3 * Possibly this is while Instance2 is warming up * AFAICT, Instance1 is taking a coffee break The net result is that I have an idle website with 1 user (me) clicking around and I've already gotten multiple 20s pauses and three instances. Something is seriously wrong here. Whether or not it's rational to have so many instances started, pending requests shouldn't be shunted to non-warmed-up servers, right? I've tried upping the min latency to a high value to see if this improves the situation. If this works... shouldn't min latency *always* be as high as the startup time for an instance? I know it's been said before, but it needs to be said again... the guidance for scheduler configuration is really, really inadequate. Jeff -- 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/-/zULJyO6VtHwJ. 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.
[appengine-java] Task Queues: Transient Error
Hi, When I try to use task queues, I got this error: 1.357137646255836705].stdout: Transient error, please try again. For two days, it's been like this, and I couldn't find any answer. Can someone help me with this? Any help will be appreciated. -- 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/-/G7EyrILv7M4J. 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] Deploy Hangs - Please help
I am getting stuck when deploy. I get the following message 52% Initializing precompilation... 90% Deploying new version. 95% Will check again in 1 seconds. 98% Will check again in 2 seconds. 99% Will check again in 4 seconds. 99% Will check again in 8 seconds. 99% Will check again in 16 seconds. 99% Will check again in 32 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. -- 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: publishing html files
any thoughts on google cloud storage? Thankx and Regards Vik Founder http://www.sakshum.org http://blog.sakshum.org On Tue, Feb 28, 2012 at 12:22 AM, Matthew Jaggard matt...@jaggard.org.ukwrote: Have a look at the blobstore documentation, that might help you. However I'd be inclined to mention a naughty word Amazon (ssh!) S3 might be the best way forward. On 28 February 2012 06:32, Vik vik@gmail.com wrote: Any advise on this please? Thankx and Regards Vik Founder http://www.sakshum.org http://blog.sakshum.org On Sun, Feb 26, 2012 at 11:28 AM, Vik vik@gmail.com wrote: Hie I am generated html documents using a google text doc as template (reading it using gdata apis and then doing some text manipulation). Now, I want to publish these documents somewhere so that I can refer to others giving the url of the document (which means it would be publicly accessible). Any suggestions on how do i go about it? Like where should i host these? Thankx and Regards Vik Founder http://www.sakshum.org http://blog.sakshum.org -- 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] Deploy Hangs - Please help
looks like server side issue. retry after some time ... On Wed, Feb 29, 2012 at 11:37 AM, treguess tregu...@gmail.com wrote: I am getting stuck when deploy. I get the following message 52% Initializing precompilation... 90% Deploying new version. 95% Will check again in 1 seconds. 98% Will check again in 2 seconds. 99% Will check again in 4 seconds. 99% Will check again in 8 seconds. 99% Will check again in 16 seconds. 99% Will check again in 32 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. -- 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.
[appengine-java] Re: Deploy Hangs - Please help
Thank you!. I am stuck here. On Feb 28, 10:36 pm, Prashant antsh...@gmail.com wrote: looks like server side issue. retry after some time ... On Wed, Feb 29, 2012 at 11:37 AM, treguess tregu...@gmail.com wrote: I am getting stuck when deploy. I get the following message 52% Initializing precompilation... 90% Deploying new version. 95% Will check again in 1 seconds. 98% Will check again in 2 seconds. 99% Will check again in 4 seconds. 99% Will check again in 8 seconds. 99% Will check again in 16 seconds. 99% Will check again in 32 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. 99% Will check again in 60 seconds. -- 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.
