Take a look at this post.
http://groups.google.com/group/objectify-appengine/browse_thread/thread/cc8148ca57ea440c
I had the same problem, and the answer is to use cursors and set a
deadline for yourself that fits within the time you are seeing will
work before the DataStore deadline is reached.
I just had this discussion with well connected people at Google. That
is the guarantee that they gave us (a very large visible GAE
implementation) and we (and they) are banking on it. I have suggested
a change to their documentation to explicitly state such a guarantee.
Test it for yourself. One
The user service will always return null when cron is calling. The
way to tell that cron is calling is to check for the "X-AppEngine-
Cron" header. It is set by the cron service and is stripped from all
other calls to your URLs. That is the best you can do until the GAE
cron service is better in
Me Too!
On Aug 19, 10:34 pm, culov wrote:
> havent been able to deploy in the last hour...
>
> On Aug 19, 8:24 pm, Shawn Brown wrote:
>
>
>
>
>
>
>
> > Hello,
>
> > I consistently get:
>
> > Unable to update:
> > java.io.IOException: Error posting to
> > URL:https://appengine.google.com/api/app
Why is GPE requiring that I keep appengine-web.xml around so it can
store the appid and version when that info is already stored in my
app.yaml? I drank the koolaid and use .yaml files wherever I can.
Please change GPE to store/read the app meta-data from appengine-
web.xml or app.yaml - whichever
