[google-appengine] Re: App stuck in Awaiting Recurring Charge Cancellation, re-enable billing?
Argh. This is like limbo/punishment! I turned on Billing because, thanks to some dev work, I blew through the free quota. I turned it off the following day (after midnight) and it seems the quota did not get re-set. Why does it take so long to Cancel billing? I'm now stuck with an app that is broken. I'd like to turn it back on immediately (or get the quota reset properly) I would be very grateful for some quick help/support. I'll even pay! :/ Tom -- 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.
Re: [google-appengine] Re: Error code 202
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.
[google-appengine] Re: Outages?
I was crying until I read Brandon's email. Once I finish laughing, I will resume crying - and thinking about a desperate flee to another host. I've been getting many of these over the past week, I'm starting to pull my hair out. I cannot reproduce locally and I've no idea what is causing it as it's pretty intermittent. It does seem to happen more frequently with static file requests (images and javascript, etc). 2012-03-08 00:57:26.492 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) -- 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.
[google-appengine] Re: Error code 202
I'm getting these 202 errors also. It's driving me nuts. Most of the requests are relatively benign looking (request for a static image). Tom -- 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.
[google-appengine] Request: Memcache Issue
One of the tools I use a lot with App Engine is Objectify - which makes for a simple and hassle free way of using the Datastore. The developer of this tool, gives awesome support, quick bug fixes, and a tool that takes the pain away. This is an unabashed request for your help to make that tool, and App Engine's Memcache service even better by having better support for batch gets. For a rundown on the issue, read this thread: http://groups.google.com/group/objectify-appengine/browse_frm/thread/e564deeeccedc036 If you're lazy/busy and that is tldr; it would be great if you can star this issue to help make App Engine better: http://code.google.com/p/googleappengine/issues/detail?id=4874 - Likewise, if you're not lazy and have time - or even better, work at Google and could fix it, then please considering helping out to find a solution. If you don't know anything about Objectify, there is a great overview of it here from this years GoogleIO: http://www.google.com/events/io/2011/sessions/highly-productive-gwt-rapid-development-with-app-engine-objectify-requestfactory-and-gwt-platform.html Tom -- 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.
