Re: [google-appengine] yet another pending latency question

[Jeff Schnitzer]

You probably aren't going to like this tip but:

I find that any deviation from Auto/Auto produces a horrible UX.  I
haven't done a great deal of experimentation but all preliminary
results have been bad - lots of unnecessary instance starts, many of
which block user-facing requests.  All on a nearly idle application.
At this point I have taped over those sliders like you would a
lightswitch: DO NOT TOUCH.

The behavior of the scheduler is opaque, so those sliders act as
unpredictable inputs to a chinese puzzle whose only perceptible
outputs are tortured screams from your website visitors.  It's hard to
imagine a way to win at this game.

Some official transparency as to the actual behavior of the scheduler
would help out a lot.

Jeff

On Sat, Mar 10, 2012 at 9:23 PM, Peter Warren  wrote:
> I'm trying to understand why app engine spawns new instances of our
> app given our settings and a miniscule load of 7 requests from one
> client.
>
> Our application settings are:
> min idle instances: 3
> max idle instances: 3
> min pending latency: 15 secs
> max pending latency: automatic
>
> We run a client-based web app that initially makes a series of
> requests to our app engine instance(s). In the case I'm concerned with
> there are 7 requests that all take well under 15 seconds. According to
> the app engine instance logs the times are: 36ms, 207ms, 52ms, 160ms,
> 624ms, 1405ms, 3232ms.
>
> There are no other requests being executed against that app; all the
> response times are *well* under 15 seconds, and yet app engine spawns
> 3 new app instances. Why?
>
> In fact the app engine logs show 6 requests being serviced, then 1 new
> app instance spawned, then the 7th request serviced, then another 2
> app instances spawned.
>
> Our app gets very little traffic, but when a new client app is loaded
> in a browser somewhere between 3 & 7 requests are sent to app engine.
> I'm trying to keep app engine from launching new instances of our app
> since the 3 resident instances should be more than capable of handling
> our traffic volume, and spawning new instances kills the response
> time.
>
> Thanks for any tips!
>
> Peter
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to 
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/google-appengine?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: yet another pending latency question

[Peter Warren]

Additionally I just changed the max pending latency setting to 15 secs
and still see app engine spawning new instances.

Given a min latency of 15 secs and a max latency of 15 secs, I would
think that app engine would definitely not spawn a new instance until
a request had been in the queue for 15 secs.

In my latest test I see 5 requests taking under 500 ms, then app
engine spawns a new instance, then the final 2 requests are serviced,
taking 19.5 secs each!

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] My expirencie with python 2.7 and others

[Daniel Kramer]

Got it.  I've flipped my app over to 2.7 thread safe.. we'll see how it goes, 
so far seems to be running without error.  Early indications on the CPU seconds 
Use/Seconds is still showing a similar ratio between Total CPU and API Calls 
CPU.. shouldn't I expect those lines to come closer together?


On Mar 10, 2012, at 9:52 AM, Brandon Wirtz wrote:

> Most of your CPU is API calls. So moving to thread safe should help you a 
> lot.  Orange is your API CPU usage, and Blue is your total.  So about 75% of 
> your CPU is API, implying that your app does a lot of waiting on API’s…
> 
> 
>  
> From: google-appengine@googlegroups.com 
> [mailto:google-appengine@googlegroups.com] On Behalf Of Daniel
> Sent: Saturday, March 10, 2012 1:12 AM
> To: google-appengine@googlegroups.com
> Subject: Re: [google-appengine] My expirencie with python 2.7 and others
>  
> Hey Brandon.  I'm not clear how to read that graph.  Here's what I'm seeing 
> on my app, how do I interpret this and know if 2.7 is might help me?
>  
>  
> 
> 
>  
> 
> On Thursday, March 8, 2012 11:36:21 PM UTC-8, Brandon Wirtz wrote:
> Dashboard, CPU Seconds Used/Second Compare the Blue to the orange.
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Google App Engine" group.
> To view this discussion on the web visit 
> https://groups.google.com/d/msg/google-appengine/-/63jINNx8o7cJ.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to 
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/google-appengine?hl=en.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to 
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/google-appengine?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: 500 errors + high latency + please communicate with us

[cz]

My app (adb2) is getting over quota errors and is no longer serving
requests. This has never happened before. According to the dashboard
my app has used 34 instance hours to process under 100 requests which
I can't imagine is possible under normal circumstances (especially
since the app doesn't use much of the service APIs or datastore).
Despite the app's low traffic there are a number of people that depend
on using it so I hope Google can look into this.

Just a little side note: There seems to be more and more recognition
that Google's lack of support for paid services is getting to be kind
of a drag. Even the el cheapo $4/mo hosting services have trouble
ticket systems and respond pretty quickly to issues. It's nice that
some of the developer support team (ie Ikai) follow up on some things
but not having a real support system is pretty janky. And before
someone says "oh but you can sign up for premier support!", it's just
not affordable for small projects.

In general GAE has been a great platform to build apps for and I
really appreciate it, but now that I'm paying for it I feel like I can
complain a little...

thanks,
- Claude

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: 500 errors + high latency + please communicate with us

[nischalshetty]

We too are facing a lot of 500 errors for our app with app id : 
'justunfollow'  

On Friday, March 9, 2012 6:10:20 PM UTC+5:30, Nikolai wrote:
>
>
> 
> this is so wrong. I dont see any of these problems reflected in the 
> appengine system status. I don't understand why there is zero communication 
> from google concerning the outages everybody in this forum is seeing right 
> now.
> This is not a small hickup, but something we (and others) are fighting 
> since 20 hours.
> Could someone from google please comment on the current issues und reflect 
> the status on the appengine status page?
>
> thank you!
> nikolai
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/LoJdAK16QskJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Outages?

[nischalshetty]

Best explanation ever.

On Wednesday, March 7, 2012 9:45:11 PM UTC+5:30, Brandon Wirtz wrote:
>
> > So, apparently, we all imagined the problem. The status page no longer
> > admits to anything.
>
> In most systems the Uptime is 100% minus the summation of the downtime of
> all other systems.  The exception to this rule is logging. When Logging
> fails to record the downtime, Uptime goes up.  As a result Google has been
> working hard to build a logging system that goes down just ahead of all
> other systems, and comes up shortly after.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/LeAHoX7YXR4J.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] yet another pending latency question

[Peter Warren]

I'm trying to understand why app engine spawns new instances of our
app given our settings and a miniscule load of 7 requests from one
client.

Our application settings are:
min idle instances: 3
max idle instances: 3
min pending latency: 15 secs
max pending latency: automatic

We run a client-based web app that initially makes a series of
requests to our app engine instance(s). In the case I'm concerned with
there are 7 requests that all take well under 15 seconds. According to
the app engine instance logs the times are: 36ms, 207ms, 52ms, 160ms,
624ms, 1405ms, 3232ms.

There are no other requests being executed against that app; all the
response times are *well* under 15 seconds, and yet app engine spawns
3 new app instances. Why?

In fact the app engine logs show 6 requests being serviced, then 1 new
app instance spawned, then the 7th request serviced, then another 2
app instances spawned.

Our app gets very little traffic, but when a new client app is loaded
in a browser somewhere between 3 & 7 requests are sent to app engine.
I'm trying to keep app engine from launching new instances of our app
since the 3 resident instances should be more than capable of handling
our traffic volume, and spawning new instances kills the response
time.

Thanks for any tips!

Peter

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Error code 202

[Mauricio Aristizabal]

Forgot to add to last post: I'm using java, HRD, Spring for MVC, JPA.  App 
id is commentousprod


On Saturday, March 10, 2012 6:17:43 PM UTC-8, Mauricio Aristizabal wrote:
>
> I'm getting 203s as well still, and what I'm seeing might be insightful to 
> the G team.  Below are log entries for 3 failures.  All 3 happened in the 
> same page load (page request itself returned fine, and all 50 or so 
> resources loaded fine except these).  Of course, the user experience is 
> that the whole page is blank for about 5 minutes until these 3 fail and the 
> browser finally draws whatever it can and 'finishes'.  So from the user 
> perspective the page took 5 minutes to load (and looks funny).
>
> The interesting thing is that one request was a simple png file in my 
> resources directory, another was a .js file that is actually in a jar, and 
> the third was an xhr call that returns json (and involves db reads). 
>  Also.. I got other failures over an hour period, typically 1-3 resources, 
> and not the same ones. 
>
> ---
>
> 2012-03-10 16:35:47.306 /resources/images/body-background-gradient.png 500 
> 89603ms 0kb Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) 
> AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.65 Safari/535.11
>
> 67.49.52.74 - - [10/Mar/2012:16:35:47 -0800] "GET 
> /resources/images/body-background-gradient.png HTTP/1.1" 500 0 "
> http://www.commentous.com/f/f/month"; "Mozilla/5.0 (Macintosh; Intel Mac 
> OS X 10_7_2) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.65 
> Safari/535.11" "www.commentous.com" ms=89604 cpu_ms=70316 api_cpu_ms=0 
> cpm_usd=1.953321 exit_code=203 
> instance=00c61b117ccac38353c47d5376339060aca685
>
> I 2012-03-10 16:35:47.287
>
> The process handling this request unexpectedly died. This is likely to 
> cause a new process to be used for the next request to your application. 
> (Error code 203)
>
>
> 2012-03-10 16:35:47.288 /users/unreadcounts 500 89154ms 0kb Mozilla/5.0 
> (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.11 (KHTML, like Gecko) 
> Chrome/17.0.963.65 Safari/535.11
>
> 67.49.52.74 - - [10/Mar/2012:16:35:47 -0800] "GET /users/unreadcounts 
> HTTP/1.1" 500 0 "http://www.commentous.com/f/f/month"; "Mozilla/5.0 
> (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.11 (KHTML, like Gecko) 
> Chrome/17.0.963.65 Safari/535.11" "www.commentous.com" ms=89154 cpu_ms=0 
> api_cpu_ms=0 cpm_usd=0.000102 exit_code=203 
> instance=00c61b117ccac38353c47d5376339060aca685
>
> I 2012-03-10 16:35:47.286
>
> The process handling this request unexpectedly died. This is likely to 
> cause a new process to be used for the next request to your application. 
> (Error code 203)
>
>
> 2012-03-10 16:35:47.287 /resources/dijit/form/FilteringSelect.js 500 
> 89140ms 0kb Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) 
> AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.65 Safari/535.11
>
> 67.49.52.74 - - [10/Mar/2012:16:35:47 -0800] "GET 
> /resources/dijit/form/FilteringSelect.js HTTP/1.1" 500 0 "
> http://www.commentous.com/f/f/month"; "Mozilla/5.0 (Macintosh; Intel Mac 
> OS X 10_7_2) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.65 
> Safari/535.11" "www.commentous.com" ms=89141 cpu_ms=0 api_cpu_ms=0 
> cpm_usd=0.96 pending_ms=1343 exit_code=203 
> instance=00c61b117ccac38353c47d5376339060aca685
>
> I 2012-03-10 16:35:47.286
>
> The process handling this request unexpectedly died. This is likely to 
> cause a new process to be used for the next request to your application. 
> (Error code 203)
>
> ---
>
>
>
>
> On Saturday, March 10, 2012 10:44:31 AM UTC-8, Kyle Baley wrote:
>>
>> We've been getting these errors since Feb. 13. We did a deployment on 
>> that day and I've been tracing through the code trying to see if there's 
>> something in there that would cause this to no avail.
>>
>> Our app is technically HR but we don't have any data in it. The app makes 
>> API calls to another AppEngine app mostly via URLFetch. 
>>
>> That said, the errors occur almost exclusively on static files. Here's a 
>> sample:
>>
>>
>>1.  2012-03-10 11:42:06.052 /images/separator2.gif 500 124544ms 0kb 
>> Mozilla/5.0 
>>(X11; CrOS i686 1412.205.0) AppleWebKit/535.11 (KHTML, like Gecko) 
>>Chrome/17.0.963.60 Safari/535.11 
>>
>>166.248.1.87 - - [10/Mar/2012:08:42:06 -0800] "GET /images/separator2.gif 
>> HTTP/1.1" 500 0 "http://www.bookedin.net/multimedia-solutions-llc"; 
>> "Mozilla/5.0 (X11; CrOS i686 1412.205.0) AppleWebKit/535.11 (KHTML, like 
>> Gecko) Chrome/17.0.963.60 Safari/535.11" "www.bookedin.net" ms=124544 
>> cpu_ms=0 api_cpu_ms=0 cpm_usd=0.58 exit_code=202 instance=
>>
>> 2.  W 2012-03-10 11:42:06.051  
>>
>>A problem was encountered with the process that handled this request, 
>> causing it to exit. This is likely to cause a new process to be used for the 
>> next request to your application. (Error code 202)
>>
>> 
>>
>> A request to that same image two mi

[google-appengine] Re: Error code 202

[Mauricio Aristizabal]

I'm getting 203s as well still, and what I'm seeing might be insightful to 
the G team.  Below are log entries for 3 failures.  All 3 happened in the 
same page load (page request itself returned fine, and all 50 or so 
resources loaded fine except these).  Of course, the user experience is 
that the whole page is blank for about 5 minutes until these 3 fail and the 
browser finally draws whatever it can and 'finishes'.  So from the user 
perspective the page took 5 minutes to load (and looks funny).

The interesting thing is that one request was a simple png file in my 
resources directory, another was a .js file that is actually in a jar, and 
the third was an xhr call that returns json (and involves db reads). 
 Also.. I got other failures over an hour period, typically 1-3 resources, 
and not the same ones. 

---

2012-03-10 16:35:47.306 /resources/images/body-background-gradient.png 500 
89603ms 0kb Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) 
AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.65 Safari/535.11

67.49.52.74 - - [10/Mar/2012:16:35:47 -0800] "GET 
/resources/images/body-background-gradient.png HTTP/1.1" 500 0 "
http://www.commentous.com/f/f/month"; "Mozilla/5.0 (Macintosh; Intel Mac OS 
X 10_7_2) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.65 
Safari/535.11" "www.commentous.com" ms=89604 cpu_ms=70316 api_cpu_ms=0 
cpm_usd=1.953321 exit_code=203 
instance=00c61b117ccac38353c47d5376339060aca685

I 2012-03-10 16:35:47.287

The process handling this request unexpectedly died. This is likely to 
cause a new process to be used for the next request to your application. 
(Error code 203)


2012-03-10 16:35:47.288 /users/unreadcounts 500 89154ms 0kb Mozilla/5.0 
(Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.11 (KHTML, like Gecko) 
Chrome/17.0.963.65 Safari/535.11

67.49.52.74 - - [10/Mar/2012:16:35:47 -0800] "GET /users/unreadcounts 
HTTP/1.1" 500 0 "http://www.commentous.com/f/f/month"; "Mozilla/5.0 
(Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.11 (KHTML, like Gecko) 
Chrome/17.0.963.65 Safari/535.11" "www.commentous.com" ms=89154 cpu_ms=0 
api_cpu_ms=0 cpm_usd=0.000102 exit_code=203 
instance=00c61b117ccac38353c47d5376339060aca685

I 2012-03-10 16:35:47.286

The process handling this request unexpectedly died. This is likely to 
cause a new process to be used for the next request to your application. 
(Error code 203)


2012-03-10 16:35:47.287 /resources/dijit/form/FilteringSelect.js 500 
89140ms 0kb Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) 
AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.65 Safari/535.11

67.49.52.74 - - [10/Mar/2012:16:35:47 -0800] "GET 
/resources/dijit/form/FilteringSelect.js HTTP/1.1" 500 0 "
http://www.commentous.com/f/f/month"; "Mozilla/5.0 (Macintosh; Intel Mac OS 
X 10_7_2) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.65 
Safari/535.11" "www.commentous.com" ms=89141 cpu_ms=0 api_cpu_ms=0 
cpm_usd=0.96 pending_ms=1343 exit_code=203 
instance=00c61b117ccac38353c47d5376339060aca685

I 2012-03-10 16:35:47.286

The process handling this request unexpectedly died. This is likely to 
cause a new process to be used for the next request to your application. 
(Error code 203)

---




On Saturday, March 10, 2012 10:44:31 AM UTC-8, Kyle Baley wrote:
>
> We've been getting these errors since Feb. 13. We did a deployment on that 
> day and I've been tracing through the code trying to see if there's 
> something in there that would cause this to no avail.
>
> Our app is technically HR but we don't have any data in it. The app makes 
> API calls to another AppEngine app mostly via URLFetch. 
>
> That said, the errors occur almost exclusively on static files. Here's a 
> sample:
>
>
>1.  2012-03-10 11:42:06.052 /images/separator2.gif 500 124544ms 0kb 
> Mozilla/5.0 
>(X11; CrOS i686 1412.205.0) AppleWebKit/535.11 (KHTML, like Gecko) 
>Chrome/17.0.963.60 Safari/535.11 
>
>166.248.1.87 - - [10/Mar/2012:08:42:06 -0800] "GET /images/separator2.gif 
> HTTP/1.1" 500 0 "http://www.bookedin.net/multimedia-solutions-llc"; 
> "Mozilla/5.0 (X11; CrOS i686 1412.205.0) AppleWebKit/535.11 (KHTML, like 
> Gecko) Chrome/17.0.963.60 Safari/535.11" "www.bookedin.net" ms=124544 
> cpu_ms=0 api_cpu_ms=0 cpm_usd=0.58 exit_code=202 instance=
>
> 2.  W 2012-03-10 11:42:06.051  
>
>A problem was encountered with the process that handled this request, 
> causing it to exit. This is likely to cause a new process to be used for the 
> next request to your application. (Error code 202)
>
> 
>
> A request to that same image two minutes earlier (on the same instance) 
> returned a 200. AppEngine ID is gunton-prod.
>
> We're using Java. All requests are filtered through a servlet module via 
> Guice but we let requests for static files pass through. Nothing in our 
> configuration changed in the deployment we did. We're getting the problem 
> daily though intermitte

Re: [google-appengine] Re: Outages?

[Amit Sangani]

appid: textyserver

Still getting lots of exceptions, mainly:

1) com.google.apphosting.runtime.HardDeadlineExceededError exceptions, 
2) Failed startup of context 
com.google.apphosting.utils.jetty.RuntimeAppEngineWebAppContext
3) javax.jdo.JDOException: Transaction failed to commit at 
org.datanucleus.jdo.NucleusJDOHelper.getJDOExceptionForNucleusException(NucleusJDOHelper.java:419)
 
at 
org.datanucleus.jdo.JDOPersistenceManager.close(JDOPersistenceManager.java:281) 

Status page is saying everything is normal - 
http://code.google.com/status/appengine which does not seem true.

Please let us know if you need more information. 

thanks!
Amit

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/8NS6YYPFVtkJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Lots of HTTP 500 errors and all instances restarted by GAE!

[Amit Sangani]

appid: textyserver

Getting lots of:

1) com.google.apphosting.runtime.HardDeadlineExceededError exceptions, 
2) Failed startup of context 
com.google.apphosting.utils.jetty.RuntimeAppEngineWebAppContext
3) javax.jdo.JDOException: Transaction failed to commit at 
org.datanucleus.jdo.NucleusJDOHelper.getJDOExceptionForNucleusException(NucleusJDOHelper.java:419)
 
at 
org.datanucleus.jdo.JDOPersistenceManager.close(JDOPersistenceManager.java:281) 

Status page is saying everything is normal - 
http://code.google.com/status/appengine which does not seem true.

Please let us know if you need more information. 

-Amit



>  

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/m8rCEtBWbCkJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: 500 errors + high latency + please communicate with us

[Amit Sangani]

Hi Ikai & Google team,

Getting lots of 500s like others have experienced. Now mainly getting 
DatastoreTimeoutException...

com.google.appengine.api.datastore.DatastoreTimeoutException: 
at 
com.google.appengine.api.datastore.DatastoreApiHelper.translateError(DatastoreApiHelper.java:46)
at 
com.google.appengine.api.datastore.DatastoreApiHelper$1.convertException(DatastoreApiHelper.java:76)
at 
com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:106)
at 
com.google.appengine.api.datastore.FutureHelper$CumulativeAggregateFuture.get(FutureHelper.java:145)
at 
com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:90)
at 
com.google.appengine.api.datastore.FutureHelper.getInternal(FutureHelper.java:72)
at 
com.google.appengine.api.datastore.FutureHelper.quietGet(FutureHelper.java:33)
at 
com.google.appengine.api.datastore.DatastoreServiceImpl$2.runInternal(DatastoreServiceImpl.java:113)
at 
com.google.appengine.api.datastore.DatastoreServiceImpl$2.runInternal(DatastoreServiceImpl.java:110)
at 
com.google.appengine.api.datastore.TransactionRunner.runInTransaction(TransactionRunner.java:31)
at 
com.google.appengine.api.datastore.DatastoreServiceImpl.put(DatastoreServiceImpl.java:110)
at 
com.google.appengine.api.datastore.DatastoreServiceImpl.put(DatastoreServiceImpl.java:94)


Please fix it as this has been going on for last 48 hours. thanks!

-Amit
appid: textyserver

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/oMDdQnGFmJYJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Error code 202

[Kyle Baley]

We've been getting these errors since Feb. 13. We did a deployment on that 
day and I've been tracing through the code trying to see if there's 
something in there that would cause this to no avail.

Our app is technically HR but we don't have any data in it. The app makes 
API calls to another AppEngine app mostly via URLFetch. 

That said, the errors occur almost exclusively on static files. Here's a 
sample:


   1.  2012-03-10 11:42:06.052 /images/separator2.gif 500 124544ms 0kb 
Mozilla/5.0 
   (X11; CrOS i686 1412.205.0) AppleWebKit/535.11 (KHTML, like Gecko) 
   Chrome/17.0.963.60 Safari/535.11 
   
   166.248.1.87 - - [10/Mar/2012:08:42:06 -0800] "GET /images/separator2.gif 
HTTP/1.1" 500 0 "http://www.bookedin.net/multimedia-solutions-llc"; "Mozilla/5.0 
(X11; CrOS i686 1412.205.0) AppleWebKit/535.11 (KHTML, like Gecko) 
Chrome/17.0.963.60 Safari/535.11" "www.bookedin.net" ms=124544 cpu_ms=0 
api_cpu_ms=0 cpm_usd=0.58 exit_code=202 instance=
   
2.  W 2012-03-10 11:42:06.051  
   
   A problem was encountered with the process that handled this request, 
causing it to exit. This is likely to cause a new process to be used for the 
next request to your application. (Error code 202)
   


A request to that same image two minutes earlier (on the same instance) 
returned a 200. AppEngine ID is gunton-prod.

We're using Java. All requests are filtered through a servlet module via 
Guice but we let requests for static files pass through. Nothing in our 
configuration changed in the deployment we did. We're getting the problem 
daily though intermittently. 25 - 30 failures today out of over 1000 
requests for these images. 

The other AppEngine app we have is also HR and Java. It's by far the more 
heavily used one. Haven't seen any issues with it.

Happy to provide more details if you want to contact me.

On Wednesday, March 7, 2012 4:19:15 AM UTC-5, tarun2000 wrote:
>
>
> I keep getting:  A problem was encountered with the process that handled 
> this request, causing it to exit. This is likely to cause a new process to 
> be used for the next request to your application. (Error code 202)
>
> It seems like the issue happens right after uploading a new version or on 
> cold start.  It seems to disappear after a while.  The rpcs that fail may 
> be returning a lot of data.  Any idea what's wrong?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/oAUFHHPFJXUJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

RE: [google-appengine] Re: Throttling and whitelisting

[Brandon Wirtz]

>My only concern is that there was no response from GAE team to resolve
sooner this mystery.

 

Support is not guaranteed unless you pony up for the support contract.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

RE: [google-appengine] My expirencie with python 2.7 and others

[Brandon Wirtz]

Most of your CPU is API calls. So moving to thread safe should help you a
lot.  Orange is your API CPU usage, and Blue is your total.  So about 75% of
your CPU is API, implying that your app does a lot of waiting on API's.




 

From: google-appengine@googlegroups.com
[mailto:google-appengine@googlegroups.com] On Behalf Of Daniel
Sent: Saturday, March 10, 2012 1:12 AM
To: google-appengine@googlegroups.com
Subject: Re: [google-appengine] My expirencie with python 2.7 and others

 

Hey Brandon.  I'm not clear how to read that graph.  Here's what I'm seeing
on my app, how do I interpret this and know if 2.7 is might help me?

 

 

 
 

 


On Thursday, March 8, 2012 11:36:21 PM UTC-8, Brandon Wirtz wrote:

Dashboard, CPU Seconds Used/Second Compare the Blue to the orange.

-- 
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/63jINNx8o7cJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Javaland scheduler behavior

[Marcel Manz]

Additional comment:

Just while I was writing my previous message, additional frontend instances 
got started and the request counter on the resident instance did not change 
at all. 

The resident instance seems to be completely useless at the moment, as the 
scheduler started additional instances (keeping the request pending for the 
start up time), not having directed the request to the resident instance 
for immediate processing.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/7EqYyMB9-jcJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Javaland scheduler behavior

[Marcel Manz]

Jeff,

I'm seeing a very similar pattern in my threadsafe enabled Java-HRD app 
which does something between 1 to 20 QPS.

I was experimenting with various idle instance settings and pending 
latency, and could not overcome this
problem unless I allowed app engine to keep around 6 instances idle for my 
app (which is far too many). In my case the scheduler begins
to start new instances even instance 1 is just around 1 QPS and no request 
(or very little) are sent to the resident instance which is just snoozing 
around (0.000 QPS / 0.0 ms Latency).

I've also tried changing the frontend instance class from F1 to F2 to give 
it double-CPU power, but also this seemed to have little, if not no effect 
at all.

As I can control where requests to my app are sent to, I was shutting down 
all frontend instances and experimented in moving all to dynamic backends, 
where the backend instance view reports each instance's CPU usage (why is 
CPU load not listed for frontend instances?). In this case mostly my app 
served out of 1 dynamic B1 backend, which did not go over 20% CPU usage. 
Still, the scheduler several times per hour started at least 1 or 2 
additional backend instances for no reason.

Since there is no way in controlling how quickly dynamic backends get 
shutdown (unless my app sends some keep-alive requests to them), the 
backend scheduler very quickly shut them down again, just so that another 
backend got started again during the 15-minute window one needs to 
additionally pay for backend shutdowns. -> IMHO app engine should make 
dynamic backend shutdown-times configurable.

In backend mode (same instance class), my app was able to serve with either 
1 or 2 instances (compared to 3 - 6 in frontend mode), however the frequent 
starts and stops of dynamic backends made me switch back to frontend mode, 
as the 15-minute window quickly accumulates costs. (I can't use 
permanent-backends, due to unpredictable traffic spikes which require 
additional instances to come up).

Marcel



On Friday, March 9, 2012 4:53:32 AM UTC+1, Jason Collins wrote:
>
> Jeff, I see very similar behaviour in pythonland - i.e., the resident 
> instance gets almost no traffic. I opened an Enterprise support ticket 
> on the topic, and I got the following response: 
>
> "the Resident instances are kept alive by the GAE scheduler for long 
> periods in order to attend to new requests whenever there are no 
> Dynamic instances to serve them. In this way, the request does not 
> have to wait for the instance creation, thus, the latency of creating 
> the instance is avoided. 
> However, as soon as the new Dynamic instance is up and running, it 
> starts getting requests and the Resident instance turns idle again, 
> until the app sees more traffic than its available Dynamic instances 
> are able to serve." 
>
> Frankly, I'm not totally sure when the resident instances actually get 
> traffic. I flipped on a resident instance just so that I could get 
> warmup requests back (they are only issued if you have resident 
> instances now), but now I have an instance floating around doing very, 
> very little work. 
>
> It just seems wrong to me. 
> j 
>
>
>
On Friday, March 9, 2012 4:53:32 AM UTC+1, Jason Collins wrote:
>
> Jeff, I see very similar behaviour in pythonland - i.e., the resident 
> instance gets almost no traffic. I opened an Enterprise support ticket 
> on the topic, and I got the following response: 
>
> "the Resident instances are kept alive by the GAE scheduler for long 
> periods in order to attend to new requests whenever there are no 
> Dynamic instances to serve them. In this way, the request does not 
> have to wait for the instance creation, thus, the latency of creating 
> the instance is avoided. 
> However, as soon as the new Dynamic instance is up and running, it 
> starts getting requests and the Resident instance turns idle again, 
> until the app sees more traffic than its available Dynamic instances 
> are able to serve." 
>
> Frankly, I'm not totally sure when the resident instances actually get 
> traffic. I flipped on a resident instance just so that I could get 
> warmup requests back (they are only issued if you have resident 
> instances now), but now I have an instance floating around doing very, 
> very little work. 
>
> It just seems wrong to me. 
> j 
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/Uv-7dNtUB-cJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Error code 202

[Tom Carchrae]

I can also confirm the appearance of 203 errors again - which I had
seen lots of earlier this week.

Tom

On Sat, Mar 10, 2012 at 1:09 AM, tarun2000  wrote:
> My issue is still not resolved. I am now getting a 203 instead of a
> 202 during what appears to be a cold start.  The logs indicate that
> the gwt rpcs timeout.  When I refresh, everything seems to work until
> an instance is brought up again.
>
> 2012-03-10 00:59:38.235 *** 500 89571ms 0kb Mozilla/5.0 (X11;
> Linux i686) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.78
> Safari/535.11
> 128.12.114.16 - tarun [10/Mar/2012:00:59:38 -0800] "POST **
> HTTP/1.1" 500 106 "http://taruntest.webaleppo.appspot.com/"; "Mozilla/
> 5.0 (X11; Linux i686) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/
> 17.0.963.78 Safari/535.11" "taruntest.webaleppo.appspot.com" ms=89572
> cpu_ms=0 api_cpu_ms=0 cpm_usd=0.000204 exit_code=203
> instance=00c61b117c8629aa9ec396298c1de07ab8e3
> I 2012-03-10 00:59:38.234
> The process handling this request unexpectedly died. This is likely to
> cause a new process to be used for the next request to your
> application. (Error code 203)
>
> I am running HRD, but the error occurs even when there is no datastore
> access in the call.  The commonality in the failures seems to be use
> of gwt rpc.  For google engineers with access to my logs, the entries
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Mail quota Problem

[Jonathan]

I've a similar problem: after the first 100 recipients the delivery is 
blocked. After 24hours there is a reset , and so on.
I have 10$/day budget but it does not help at all. The limit is 100/24h.

app-id: or-point

On Sunday, February 12, 2012 7:39:44 AM UTC+2, Robert Kluin wrote:
>
> They've been having a number of issues related to email quotas / usage
> display.  You might file an issue with your appid so they can take a
> look.
>
>
> Robert
>
>
> On Sat, Feb 11, 2012 at 08:35, partnerke...@hotmail.com
>  wrote:
> > Hello
> > Recipients Emailed %100 fills up quickly.
> > Estimated cost for the last 6 hours:$0.00* / $150.00 active. But it
> > does not send.
> >
> > The problem is what do you think?
> >
> > Thank You
> >
> > --
> > You received this message because you are subscribed to the Google 
> Groups "Google App Engine" group.
> > To post to this group, send email to google-appengine@googlegroups.com.
> > To unsubscribe from this group, send email to 
> google-appengine+unsubscr...@googlegroups.com.
> > For more options, visit this group at 
> http://groups.google.com/group/google-appengine?hl=en.
> >
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/Q4yiFNekUbgJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Outages?

[Alexander Trakhimenok]

Alex,

I believe it's better wait till Monday before starting a new thread as 
otherwise it would not get much attention. By Monday we would get actual 
billing history data for the 9th of March so we would be able to raise  a 
case with some data so we can prove a pattern.

In meantime I belive we can fill a spreadsheet - I've created a template: 
https://docs.google.com/spreadsheet/ccc?key=0AtxJ_-1aIO7idEhYT3pyLVZ4R3F0cGdTMFhyZkswVWc

Also we can raise and issue in the issue tracker.

Alex

On Saturday, 10 March 2012 06:20:40 UTC-4, Alex Popescu wrote:
>
> I'm also interested to find out how to get a refund after the reports I've 
> submitted in the last 24h showing in this thread [1] that since the 
> maintenance window Google AppEngine itself has been the only one 
> responsible for consuming my quota. While historical stats have also been 
> wiped out since the last maintenance I still have the billing history which 
> can be used as historical data.
>
> Alexander, should we start a separate thread to get this info from Google?
>
> [1] 
> https://groups.google.com/forum/?fromgroups#!topic/google-appengine/hpCCA3-QR04
>
> On Saturday, March 10, 2012 6:09:02 AM UTC+2, Alexander Trakhimenok wrote:
>>
>> Our Python 2.5 app "petaclasses" is still having crazy amount of 
>> instances - over 250 at the moment against normal 10-15.
>>
>> Our average costs to run the app is $25 per day - it's 4 hours till the 
>> end of the today and we already spend $154. What the  ??
>>
>> Is it policy of Google AppEngine team that we (customers) should pay for 
>> mistakes made by GAE? Any chance to get it fixed and get a refund?
>>
>> Thanks,
>> Alex
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/m8blzdjhG8kJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Throttling and whitelisting

[Matija]

Yes. There was problem with our QoS settings. This 'backup' server is 
actually used almost always internally, and this monthly backup is, let's 
say, only time that it needs to connect to outside world. So our firewall 
and vpn gateway had low QoS settings for this server. So thanks for hint. 
There was no problem on GAE or ISP side.

My only concern is that there was no response from GAE team to resolve 
sooner this mystery.

Thank you, Matija.

On Tuesday, March 6, 2012 4:03:21 PM UTC+1, Brandon Wirtz wrote:
>
> Google’s Edge will deny you if you start doing too many requests that look 
> the same.  You get a pop up fill out a captcha life is happy for 24 hours.  
> You have to work pretty hard to get these, but I have seen it.
>
> YOUR ISP may throttle you if you look like you are trying to DDoS a site. 
> I get this a LOT more than I hit Google’s edge.  If your response is slow, 
> and the bit speed slows down. It is your ISP.  If the 5XX Error page is not 
> a Google Error, it is your ISP.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/dI3vIgqTJPgJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: 500 errors + high latency + please communicate with us

[Thomas]

hi ikai! same problem here: lots of 500s, bad performance and way too many 
instances running since last week. please help us with this!

appid: typescout

many thanks!
thomas


Am Freitag, 9. März 2012 20:57:58 UTC+1 schrieb Ikai Lan:
>
> Luis, do these happen on loading requests?
>
> --
> Ikai Lan 
> Developer Programs Engineer, Google App Engine
> plus.ikailan.com
>
>
>
> On Fri, Mar 9, 2012 at 11:52 AM, Luis wrote:
>
>> We are suffering something pretty similar. Without having made any
>> kind of change either in the application configuration (in the
>> console) or the actual code (deployments), during the day we have been
>> suffering an abnormal low performance and continuous errors (500
>> server error, ExceptionInInitializerError, DeadlineExceededException.
>> Additionally we noticed that for a normal work load the total number
>> of instances created has increased significantly during the last 12
>> hours (please see attached screenshot).
>>
>> Please find log files and screenshots in the ticket we opened:
>> http://code.google.com/p/googleappengine/issues/detail?id=7113
>>
>> Our appid is reportingsuiteengine and we are using master/slave
>>
>> Thanks,
>> Luis
>>
>> On 9 mar, 20:18, "Ikai Lan (Google)"  wrote:
>> > Are you guys seeing any particular errors in the logs or other observed
>> > strange behavior? Thanks for providing an application ID, it'll make it
>> > easier for us to look into this.
>> >
>> > There seem to be several parallel issues occurring. It's still unclear 
>> to
>> > me whether or not they are related. We need to un-cross the streams.
>> >
>> > --
>> > Ikai Lan
>> > Developer Programs Engineer, Google App Engine
>> > plus.ikailan.com
>> >
>> >
>> >
>> > On Fri, Mar 9, 2012 at 7:43 AM, Amit Sangani  
>> wrote:
>> > > We are facing the same issues as others are experiencing here. High
>> > > latency, instance count sky-rocketed, lot of errors in logs
>> > > (HardDeadlineExceededError , java.lang.NoClassDefFoundError, etc).
>> > > This was working perfectly 2 days back. Ever since the last
>> > > maintenance (March 7th) GAE has been very unstable for us.
>> >
>> > > Our app id is: textyserver
>> >
>> > > On Mar 9, 6:38 am, "Sharp-Developer.Net"
>> > >  wrote:
>> > > > Our instances count sky-rocketed about 3 hours ago from usual 5-10 
>> to
>> > > over
>> > > > 500 and we exceeded our limits. We had no deployments in last 24 
>> hours.
>> >
>> > > > App ID is: petaclasses
>> >
>> > > > We are loosing money and trust of our customers and no news from 
>> Google
>> > > and
>> > > > no way to communicate - smells very bad to me.
>> >
>> > > > I love GAE but my team is pushing me to evaluate other alternatives.
>> >
>> > > > Alex
>> >
>> > > > On Friday, 9 March 2012 08:40:20 UTC-4, Nikolai wrote:
>> >
>> > > > > <
>> > >
>> https://lh6.googleusercontent.com/-8WF96dBSCf4/T1n5Cg1ePDI/BQ...>
>> > > > > this is so wrong. I dont see any of these problems reflected in 
>> the
>> > > > > appengine system status. I don't understand why there is zero
>> > > communication
>> > > > > from google concerning the outages everybody in this forum is 
>> seeing
>> > > right
>> > > > > now.
>> > > > > This is not a small hickup, but something we (and others) are 
>> fighting
>> > > > > since 20 hours.
>> > > > > Could someone from google please comment on the current issues und
>> > > reflect
>> > > > > the status on the appengine status page?
>> >
>> > > > > thank you!
>> > > > > nikolai
>> >
>> > > --
>> > > You received this message because you are subscribed to the Google 
>> Groups
>> > > "Google App Engine" group.
>> > > To post to this group, send email to 
>> google-appengine@googlegroups.com.
>> > > To unsubscribe from this group, send email to
>> > > google-appengine+unsubscr...@googlegroups.com.
>> > > For more options, visit this group at
>> > >http://groups.google.com/group/google-appengine?hl=en.- Ocultar texto 
>> de la cita -
>> >
>> > - Mostrar texto de la cita -
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Google App Engine" group.
>> To post to this group, send email to google-appengine@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> google-appengine+unsubscr...@googlegroups.com.
>> For more options, visit this group at 
>> http://groups.google.com/group/google-appengine?hl=en.
>>
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/cFCPZWAE8OYJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Google App Engine community support is moving to Stack Overflow

[BigMouth Li]

Ikai Lan於 2012年2月7日星期二UTC+8上午10時14分54秒寫道：
>
> *Hi App Engine Developers,
>
> In the last few years, the Q&A website Stack 
> Overflowhas become an invaluable tool for 
> developer communities. We’re pleased to 
> announce that we are migrating to Stack Overflow as the official channel 
> for answering development questions about Google App Engine.The 
> google-appengine  group 
> will remain open for general discussions and announcements that are better 
> suited for the groups format.
>
> We believe that Stack Overflow is better platform for sharing knowledge 
> and answering support questions given its larger community, de-duping of 
> similar questions and contributor reputation system. We also expect that 
> App Engine developers will be able to contribute and benefit from the wider 
> range of language-related information not specific to App Engine. In 
> addition, due to Stack Overflow’s use of OpenID for account management, 
> developers will not need to create a new account to participate in the 
> discussion - developers will be able to log in with any of the identity 
> providers supported by Stack Overflow, including Google Accounts.
>
> We plan on deprecating the App Engine language-specific groups, namely 
> google-appengine-pythonand
>  
> google-appengine-java. 
> The 
> google-appengine-godiscussion
>  group will continue to remain open for at least as long as the 
> Go runtime is in experimental status. 
>
> The Python and Java groups will be placed into read-only on March 5th, 
> 2012. While answering technical questions, we will begin nudging developers 
> to ask their questions on Stack Overflow using the google-app-engine 
> tag
> .
>
> Please let us know if there are any questions or concerns about this 
> announcement.
>
> Happy coding!
>
> - Ikai Lan, on behalf of the App Engine team*
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/QFf9_3RqTJgJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Outages?

[Alex Popescu]

I'm also interested to find out how to get a refund after the reports I've 
submitted in the last 24h showing in this thread [1] that since the 
maintenance window Google AppEngine itself has been the only one 
responsible for consuming my quota. While historical stats have also been 
wiped out since the last maintenance I still have the billing history which 
can be used as historical data.

Alexander, should we start a separate thread to get this info from Google?

[1] 
https://groups.google.com/forum/?fromgroups#!topic/google-appengine/hpCCA3-QR04

On Saturday, March 10, 2012 6:09:02 AM UTC+2, Alexander Trakhimenok wrote:
>
> Our Python 2.5 app "petaclasses" is still having crazy amount of instances 
> - over 250 at the moment against normal 10-15.
>
> Our average costs to run the app is $25 per day - it's 4 hours till the 
> end of the today and we already spend $154. What the  ??
>
> Is it policy of Google AppEngine team that we (customers) should pay for 
> mistakes made by GAE? Any chance to get it fixed and get a refund?
>
> Thanks,
> Alex
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/0DHFXrhqCa8J.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Issue after HRD migration: 100 email quota until first charge cleared

[Martin Waller]

I moved away from google to send out emails. My app now uses Amazon simple 
email and it seems to be fine!

Martin

Sent from my iPhone

On 10 Mar 2012, at 08:59, Jonathan  wrote:

> Hi Christina
> I've a similar problem, after the first 100 recipients the delivery is 
> blocked. After 24hours there is a reset , and so on.
> I have 10$/day budget but it does not help.
> 
> app-id: or-point
> 
> 
> On Monday, March 5, 2012 10:56:52 PM UTC+2, Christina Ilvento wrote:
> Hi Anders,
> 
> Would you please enter your M/S and HRD app-ids in the migration quota bump 
> request form at 
> https://docs.google.com/a/google.com/spreadsheet/viewform?formkey=dENESzEwNzJiZEdpQkRzTl9RNElVWUE6MQ#gid=0
>  
> 
> 
> 
> Thanks,
> Christina
> 
> On Sun, Mar 4, 2012 at 1:13 PM, Anders  wrote:
> I did a migration of an old application to the high replication
> datastore over the weekend. Everything looked fine at first but now I
> am having an issue with the email quota.
> 
> Since the email quota is 100 emails before the first charge is cleared
> and I just enabled billing on my new application I have to wait until
> the end of the week (when the first charge is made) before I am able
> to send out emails. Isn't there some way to be charged directly and
> not wait for the end of the period?
> 
> Did anyone ran into the same issue and found a solution? I am sending
> some thousand emails a day to customers so this was a very unfortunate
> consequence of the migration.
> 
> --
> You received this message because you are subscribed to the Google Groups 
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to 
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/google-appengine?hl=en.
> 
> 
> 
> 
> -- 
> 
> Christina Ilvento | Google App Engine | cilve...@google.com | (650)-201-9399
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Google App Engine" group.
> To view this discussion on the web visit 
> https://groups.google.com/d/msg/google-appengine/-/jofN1t-t1JEJ.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to 
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/google-appengine?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Error code 202

[tarun2000]

My issue is still not resolved. I am now getting a 203 instead of a
202 during what appears to be a cold start.  The logs indicate that
the gwt rpcs timeout.  When I refresh, everything seems to work until
an instance is brought up again.

2012-03-10 00:59:38.235 *** 500 89571ms 0kb Mozilla/5.0 (X11;
Linux i686) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.78
Safari/535.11
128.12.114.16 - tarun [10/Mar/2012:00:59:38 -0800] "POST **
HTTP/1.1" 500 106 "http://taruntest.webaleppo.appspot.com/"; "Mozilla/
5.0 (X11; Linux i686) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/
17.0.963.78 Safari/535.11" "taruntest.webaleppo.appspot.com" ms=89572
cpu_ms=0 api_cpu_ms=0 cpm_usd=0.000204 exit_code=203
instance=00c61b117c8629aa9ec396298c1de07ab8e3
I 2012-03-10 00:59:38.234
The process handling this request unexpectedly died. This is likely to
cause a new process to be used for the next request to your
application. (Error code 203)

I am running HRD, but the error occurs even when there is no datastore
access in the call.  The commonality in the failures seems to be use
of gwt rpc.  For google engineers with access to my logs, the entries
can be found by filtering for device-.

On Mar 9, 3:04 pm, "Ikai Lan (Google)"  wrote:
> I've taken a look at some of the High Replication app IDs posted publicly
> and haven't found instances of this (instances exiting because of error
> code 202) recently. It looks to have stabilized as of ~15 hours ago. If you
> have a master/slave application that continues to exhibit this behavior,
> there might be a band aid we can apply, but please don't ask for it unless
> you are still seeing issues since there could be unintended consequences.
>
> Side note: there are a few things going on at the same time, so if you are
> NOT seeing the symptoms reported in this thread (Error Code 202 exits),
> please don't post to this thread - you're just making it harder to collect
> information and address the issue.
>
> --
> Ikai Lan
> Developer Programs Engineer, Google App Engine
> plus.ikailan.com
>
> On Fri, Mar 9, 2012 at 9:09 AM, Takashi Matsuo ♟  wrote:
>
>
>
>
>
>
>
> > Sorry to chiming in a bit late here.
> > If anyone is still suffering from (Error code 202), please let me know
> > your app-ids and the time of the occurrence.
>
> > I'll try my best to solve the issue.
>
> > -- Takashi
>
> > On Sat, Mar 10, 2012 at 12:25 AM, Ronoaldo José de Lana Pereira
> >  wrote:
> > > Same here, my apps is Java, concurrent requests enabled, on MS (sadly
> > ...)
>
> > > Em sexta-feira, 9 de março de 2012 08h27min15s UTC-3, Nikolai escreveu:
>
> > >> +1
> > >> same here
>
> > >> Am Mittwoch, 7. März 2012 10:19:15 UTC+1 schrieb tarun2000:
>
> > >>> I keep getting:  A problem was encountered with the process that
> > handled
> > >>> this request, causing it to exit. This is likely to cause a new
> > process to
> > >>> be used for the next request to your application. (Error code 202)
>
> > >>> It seems like the issue happens right after uploading a new version or
> > on
> > >>> cold start.  It seems to disappear after a while.  The rpcs that fail
> > may be
> > >>> returning a lot of data.  Any idea what's wrong?
>
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > > "Google App Engine" group.
> > > To view this discussion on the web visit
> > >https://groups.google.com/d/msg/google-appengine/-/vCTQyKvK20gJ.
>
> > > To post to this group, send email to google-appengine@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > google-appengine+unsubscr...@googlegroups.com.
> > > For more options, visit this group at
> > >http://groups.google.com/group/google-appengine?hl=en.
>
> > --
> > Takashi Matsuo | Developer Advocate | tmat...@google.com | 03-6384-9224
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google App Engine" group.
> > To post to this group, send email to google-appengine@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-appengine+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/google-appengine?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Issue after HRD migration: 100 email quota until first charge cleared

[Jonathan]

Hi Christina
I've a similar problem, after the first 100 recipients the delivery is 
blocked. After 24hours there is a reset , and so on.
I have 10$/day budget but it does not help.

app-id: or-point


On Monday, March 5, 2012 10:56:52 PM UTC+2, Christina Ilvento wrote:
>
> Hi Anders,
>
> Would you please enter your M/S and HRD app-ids in the migration quota 
> bump request form at 
> https://docs.google.com/a/google.com/spreadsheet/viewform?formkey=dENESzEwNzJiZEdpQkRzTl9RNElVWUE6MQ#gid=0
>  
>
>
>
> Thanks,
> Christina
>
> On Sun, Mar 4, 2012 at 1:13 PM, Anders  wrote:
>
>> I did a migration of an old application to the high replication
>> datastore over the weekend. Everything looked fine at first but now I
>> am having an issue with the email quota.
>>
>> Since the email quota is 100 emails before the first charge is cleared
>> and I just enabled billing on my new application I have to wait until
>> the end of the week (when the first charge is made) before I am able
>> to send out emails. Isn't there some way to be charged directly and
>> not wait for the end of the period?
>>
>> Did anyone ran into the same issue and found a solution? I am sending
>> some thousand emails a day to customers so this was a very unfortunate
>> consequence of the migration.
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Google App Engine" group.
>> To post to this group, send email to google-appengine@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> google-appengine+unsubscr...@googlegroups.com.
>> For more options, visit this group at 
>> http://groups.google.com/group/google-appengine?hl=en.
>>
>>
>
>
> -- 
>
> Christina Ilvento | Google App Engine | cilve...@google.com | 
> (650)-201-9399
>
>
>  

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/jofN1t-t1JEJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Problem with mail quota

[Jonathan]

I've exactly the same problem, after the first 100 recipients the delivery 
is blocked. After 24hours there is a reset , and so on.
I have 10$/day budget but it does not help.

app-id: or-point



On Friday, February 10, 2012 12:22:56 AM UTC+2, Ikai Lan wrote:
>
> We're running a batch job right now to fix the issue. Stay tuned.
>
> --
> Ikai Lan 
> Developer Programs Engineer, Google App Engine
> plus.ikailan.com
>
>
>
> On Thu, Feb 9, 2012 at 2:07 PM, Greg  wrote:
>
>> I have a large (paid) quota for email, and got a quota exception two
>> hours ago. I'm guessing there was a glitch in the mail quota about
>> that time.
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Google App Engine" group.
>> To post to this group, send email to google-appengine@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> google-appengine+unsubscr...@googlegroups.com.
>> For more options, visit this group at 
>> http://groups.google.com/group/google-appengine?hl=en.
>>
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/dSqg2WEK570J.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Google App Engine Down?

[Jonathan]

I've exactly the same problem, after the first 100 recipients the mail 
delivery is blocked. After 24hours there is a reset , and so on.
I have 10$/day budget but it does not help.
app-id: or-point


On Tuesday, March 6, 2012 11:13:13 PM UTC+2, Holly Orr wrote:
>
> We are paying for the service, and should not have exceeded our limit.  It 
> keeps giving us an error stating we have possibly exceeded limit.  Also, it 
> has been exceptionally slow for the last 2 hours.


On Tuesday, March 6, 2012 11:13:13 PM UTC+2, Holly Orr wrote:
>
> We are paying for the service, and should not have exceeded our limit.  It 
> keeps giving us an error stating we have possibly exceeded limit.  Also, it 
> has been exceptionally slow for the last 2 hours.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/Hw82eaAm4FwJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: paid user, email delivered, but can't be received

[Jonathan]

I've exactly the same problem, after the first 100 recipients the delivery 
is blocked. After 24hours there is a reset , and so on.
I have 10$/day budget but it does not help.


On Thursday, March 8, 2012 5:11:38 AM UTC+2, Paco Paco wrote:
>
> The first charge was cleared, and 5000 emails are definitely within 
> the quota, and I can see that on the dashboard. 
> The first 100 recipients had received my email, but after the first 
> 100, nobody had received anything. 
> What am I supposed to do?

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/kuEWOszJjAQJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] My expirencie with python 2.7 and others

[Daniel]

Hey Brandon.  I'm not clear how to read that graph.  Here's what I'm seeing 
on my app, how do I interpret this and know if 2.7 is might help me?





On Thursday, March 8, 2012 11:36:21 PM UTC-8, Brandon Wirtz wrote:
>
> Dashboard, CPU Seconds Used/Second Compare the Blue to the orange.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/63jINNx8o7cJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.