Thank you for your reply. The log tells that it is the initialization of a 
new instance that takes longer than 60 seconds and therefore it is shut 
down. This means that no new instances could be started causing our service 
to be completely down.

The strange and unanswered part is still that our source code had been 
running for a couple of months without any change. Then this problem 
happened for 12 hours and suddenly it worked again. For the past 3 days 
everything has been working, but we still did not change the code. Not 
before, not during the down period and not after the down 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 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 message frequently, you may be 
> throwing exceptions during the initialization of your application. (Error 
> code 104)
>
>
>
> Nothing was changed in our source code on either sides. Google please 
> solve this and in the future do not beta test on real users !!!
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to