I take it back, even going to F4s (from F1s) instances are still dying and failing to come up. Sometimes they succeed, sometimes they don't. Broken broken broken.
Jeff On Mon, Apr 29, 2013 at 12:27 AM, Jeff Schnitzer <j...@infohazard.org>wrote: > Appengine is hosed right now. I'm seeing some requests go over 250 seconds > (cron requests) without successfully getting an instance off the ground. > > I temporarily switched to F4 instances, which might or might not have > helped; I have at least one instance serving. But this problem keeps > coming up over and over and over again. > > Jeff > > > On Sun, Apr 28, 2013 at 11:42 PM, Alexandru Farcaş < > alex.far...@expert-group.biz> wrote: > >> Hi Vinny, >> >> Thanks for your answer, but I am not reading/processing any ZIP file in >> my servlets. >> I have a test servlet on which I only print "OK" to output. This servlet >> also received the same exception (This is how I test if my application is >> running OK). Because I received several times error for this servlet I >> verified my app and logs. >> >> My app requests lasts for 2-3 seconds. My last deploy (on default) was >> Friday and until last night I didn't have any problems. >> >> Now it is working OK with no changes my code! >> >> Kind regards, >> Alexandru! >> >> >> On Monday, April 29, 2013 1:39:07 AM UTC+3, Vinny P wrote: >>> >>> Hello Alexandru, >>> >>> It looks like you're reading in and processing a ZIP file in your >>> servlet's init function, correct? >>> >>> Google App Engine has a warmup limit of 60 seconds - your app must fully >>> initialize (loading in libraries, running init) within 60 seconds or it >>> throws a DeadlineExceededException. Your app is going over that time limit. >>> You'll need to modify your app to move some logic out of the init portion. >>> >>> >>> ----------------- >>> -Vinny P >>> Technology & Media Advisor >>> Chicago, IL >>> >>> My Go side project: http://invalidmail.com/ >>> >>> >>> On Sunday, April 28, 2013 4:20:09 PM UTC-5, Alexandru Farcaş wrote: >>>> >>>> Here is an example of request (in the attchm). >>>> Some of them are just receiving this warning >>>> >>>> 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) >>>> >>>> -- >> 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 google-appengine+unsubscr...@googlegroups.com. >> To post to this group, send email to google-appengine@googlegroups.com. >> Visit this group at http://groups.google.com/group/google-appengine?hl=en >> . >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- 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 google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
