Same here, everything is back to normal.
On Thursday, December 12, 2013 8:38:19 PM UTC+1, Michael Collins wrote: > > And now this morning all is back to normal...gack > > On Wednesday, December 11, 2013 4:46:24 PM UTC-8, Michael Collins wrote: >> >> Spoke too soon. The stack trace was from a misguided attempt to correct >> a benign warning. >> Still getting error 121 with no stack trace. >> >> On Wednesday, December 11, 2013 4:37:00 PM UTC-8, Michael Collins wrote: >>> >>> I did just start getting a stack trace with the error 121, that should >>> help, if somebody fixed something thanks... >>> >>> >>> On Wednesday, December 11, 2013 3:31:01 PM UTC-8, Francois Masurel wrote: >>>> >>>> Hi Michael, >>>> >>>> I have exactly the same problem with one of my Java app at the moment >>>> (bblcts2). >>>> >>>> I had the same problem yesterday on another app and it lasted for more >>>> than 2 hours. It's now fixed. >>>> >>>> François >>>> >>>> On Wednesday, December 11, 2013 11:38:22 PM UTC+1, Michael Collins >>>> wrote: >>>>> >>>>> I have been working on an app for the last 5 days, all was fine until >>>>> this morning. Since then I'm getting nothing but "Error code 121" for >>>>> requests >>>>> coming from my Android devices. Web pages are being served properly. >>>>> Tried rolling back to a previous working version of the device and server >>>>> code, same problem. Tried building and deploying the pure >>>>> Android/AppEngine app, same error. >>>>> >>>>> Killed the GAE instances, cranked the GAE version, nothing helps. >>>>> >>>>> What can I do to help you figure out if it's my problem or your >>>>> problem? Below is from the pure Google sample code. >>>>> >>>>> >>>>> 1. 2013-12-11 14:08:14.625 >>>>> /_ah/spi/com.ebay.mike.test.DeviceInfoEndpoint.getDeviceInfo 500 >>>>> 2057ms 0kb Google-HTTP-Java-Client/1.16.0-rc (gzip) module=default >>>>> version=2 >>>>> >>>>> 216.113.168.148 - - [11/Dec/2013:14:08:14 -0800] "POST >>>>> /_ah/spi/com.ebay.mike.test.DeviceInfoEndpoint.getDeviceInfo HTTP/1.1" >>>>> 500 0 - "Google-HTTP-Java-Client/1.16.0-rc (gzip)" >>>>> "blue2smog.appspot.com" ms=2057 cpu_ms=1082 loading_request=1 >>>>> exit_code=121 app_engine_release=1.8.8 >>>>> instance=00c61b117c6ea0963d970075075c6b13db57d7 >>>>> <https://appengine.google.com/instances?app_id=s~blue2smog&version_id=2.372266113542667535&key=00c61b117c6ea0963d970075075c6b13db57d7#00c61b117c6ea0963d970075075c6b13db57d7> >>>>> >>>>> 2. I2013-12-11 14:08:14.573 >>>>> >>>>> This request caused a new process to be started for your application, >>>>> and thus caused your application code to be loaded for the first time. >>>>> This request may thus take longer and use more CPU than a typical request >>>>> for your application. >>>>> >>>>> 3. W2013-12-11 14:08:14.573 >>>>> >>>>> 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 121) >>>>> >>>>> >>>>> >>>>> >>>>> On Wednesday, December 11, 2013 8:54:24 AM UTC-8, >>>>> sco...@referabuyer.com wrote: >>>>>> >>>>>> We were getting a lot of these errors and eventually noticed that >>>>>> they were all happening on a particular instance(instance #19 for us). >>>>>> By >>>>>> deleting the backend that the errors were occurring on and then bringing >>>>>> it >>>>>> back up the issue was put to rest. >>>>>> >>>>> -- 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. For more options, visit https://groups.google.com/groups/opt_out.
