Ok, I've found the problem.

Actually these tasks were taking too long to execute, but not to
initialize. The weird thing is, they were returning the error with 10s
and 0ms cpu (what is not true because it took way more than 0ms cpu)
and no log messages (what usually happens with cold starts).

On Feb 17, 9:32 am, WSouza <[email protected]> wrote:
> More information,
>
> I've put a log message on the first line of doPost(), and on the few
> requests that run it takes 8-9s to print the message.
>
> On Feb 17, 9:16 am, WSouza <[email protected]> wrote:
>
>
>
> > 1 hour and still the same thing.. One thing different from "normal" is
> > that I have 200+ tasks in a queue trying to run. (but I've had more
> > than 2000 yesterday and it worked fine)
>
> > On Feb 17, 8:42 am, WSouza <[email protected]> wrote:
>
> > > Hello!
>
> > > I am getting the cold start errors at 80-90% of my requests for the
> > > past 20 minutes (they were working fine last night, no code change and
> > > there is no framework used, just plain java + low-level datastore/
> > > memcache access).
>
> > > Is anyone experiencing the same thing (maintenance today is at 5:00PM
> > > not AM, right :D)?
>
> > > Thanks,
> > > William

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
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-java?hl=en.

Reply via email to