I'm getting 203s as well still, and what I'm seeing might be insightful to the G team. Below are log entries for 3 failures. All 3 happened in the same page load (page request itself returned fine, and all 50 or so resources loaded fine except these). Of course, the user experience is that the whole page is blank for about 5 minutes until these 3 fail and the browser finally draws whatever it can and 'finishes'. So from the user perspective the page took 5 minutes to load (and looks funny).
The interesting thing is that one request was a simple png file in my resources directory, another was a .js file that is actually in a jar, and the third was an xhr call that returns json (and involves db reads). Also.. I got other failures over an hour period, typically 1-3 resources, and not the same ones. ----------------------- 2012-03-10 16:35:47.306 /resources/images/body-background-gradient.png 500 89603ms 0kb Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.65 Safari/535.11 67.49.52.74 - - [10/Mar/2012:16:35:47 -0800] "GET /resources/images/body-background-gradient.png HTTP/1.1" 500 0 " http://www.commentous.com/f/f/month"; "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.65 Safari/535.11" "www.commentous.com" ms=89604 cpu_ms=70316 api_cpu_ms=0 cpm_usd=1.953321 exit_code=203 instance=00c61b117ccac38353c47d5376339060aca685 I 2012-03-10 16:35:47.287 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) 2012-03-10 16:35:47.288 /users/unreadcounts 500 89154ms 0kb Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.65 Safari/535.11 67.49.52.74 - - [10/Mar/2012:16:35:47 -0800] "GET /users/unreadcounts HTTP/1.1" 500 0 "http://www.commentous.com/f/f/month"; "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.65 Safari/535.11" "www.commentous.com" ms=89154 cpu_ms=0 api_cpu_ms=0 cpm_usd=0.000102 exit_code=203 instance=00c61b117ccac38353c47d5376339060aca685 I 2012-03-10 16:35:47.286 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) 2012-03-10 16:35:47.287 /resources/dijit/form/FilteringSelect.js 500 89140ms 0kb Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.65 Safari/535.11 67.49.52.74 - - [10/Mar/2012:16:35:47 -0800] "GET /resources/dijit/form/FilteringSelect.js HTTP/1.1" 500 0 " http://www.commentous.com/f/f/month"; "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.65 Safari/535.11" "www.commentous.com" ms=89141 cpu_ms=0 api_cpu_ms=0 cpm_usd=0.000096 pending_ms=1343 exit_code=203 instance=00c61b117ccac38353c47d5376339060aca685 I 2012-03-10 16:35:47.286 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) ------------------------------- On Saturday, March 10, 2012 10:44:31 AM UTC-8, Kyle Baley wrote: > > We've been getting these errors since Feb. 13. We did a deployment on that > day and I've been tracing through the code trying to see if there's > something in there that would cause this to no avail. > > Our app is technically HR but we don't have any data in it. The app makes > API calls to another AppEngine app mostly via URLFetch. > > That said, the errors occur almost exclusively on static files. Here's a > sample: > > > 1. 2012-03-10 11:42:06.052 /images/separator2.gif 500 124544ms 0kb > Mozilla/5.0 > (X11; CrOS i686 1412.205.0) AppleWebKit/535.11 (KHTML, like Gecko) > Chrome/17.0.963.60 Safari/535.11 > > 166.248.1.87 - - [10/Mar/2012:08:42:06 -0800] "GET /images/separator2.gif > HTTP/1.1" 500 0 "http://www.bookedin.net/multimedia-solutions-llc"; > "Mozilla/5.0 (X11; CrOS i686 1412.205.0) AppleWebKit/535.11 (KHTML, like > Gecko) Chrome/17.0.963.60 Safari/535.11" "www.bookedin.net" ms=124544 > cpu_ms=0 api_cpu_ms=0 cpm_usd=0.000058 exit_code=202 instance= > > 2. W 2012-03-10 11:42:06.051 > > 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 202) > > > > A request to that same image two minutes earlier (on the same instance) > returned a 200. AppEngine ID is gunton-prod. > > We're using Java. All requests are filtered through a servlet module via > Guice but we let requests for static files pass through. Nothing in our > configuration changed in the deployment we did. We're getting the problem > daily though intermittently. 25 - 30 failures today out of over 1000 > requests for these images. > > The other AppEngine app we have is also HR and Java. It's by far the more > heavily used one. Haven't seen any issues with it. > > Happy to provide more details if you want to contact me. > > On Wednesday, March 7, 2012 4:19:15 AM UTC-5, tarun2000 wrote: >> >> >> I keep getting: 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 202) >> >> It seems like the issue happens right after uploading a new version or on >> cold start. It seems to disappear after a while. The rpcs that fail may >> be returning a lot of data. Any idea what's wrong? >> > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/ByLvQkDnN_0J. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
