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 <tarunpondiche...@gmail.com> 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.
