[google-appengine] Re: Appengine is down (errorcode 104)

2013-12-16 Thread Hans Jakobsen
Having a 12 hours down period is very bad when having paying customers who expects a 24/7 service. Over a month this an up-time of only 98%. However, while our service was down, Google still claimed that everything was up and running: https://code.google.com/status/appengine Though, Google actua

[google-appengine] Re: Appengine is down (errorcode 104)

2013-12-15 Thread Hans Jakobsen
period. That leads me to think that Google is using us as beta testers for internal changes. On Thursday, December 12, 2013 9:08:56 PM UTC+1, Hans Jakobsen wrote: > > Since 3 hours ago, all requests to our appengine application fails with > this message in the log: > > A problem

[google-appengine] Appengine is down (errorcode 104)

2013-12-12 Thread Hans Jakobsen
Since 3 hours ago, all requests to our appengine application fails with this message in the log: 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. If you see this m

[google-appengine] Re: No more warmup requests!

2013-11-01 Thread Hans Jakobsen
I have a similar situation. Have set minimum idle instance to 3, but since two days ago the number of actual instances dropped to be exact one. It remains one no matter what latency the customer has and no matter what setting I have in idle instances. I did not make any changes at that time, so