(with the
dynamic high cpu use limit).
On Feb 17, 11:03 am, WSouza wrote:
> 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
.
On Feb 17, 9:32 am, WSouza 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 wrote:
>
>
>
> > 1 hour and still the sa
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 wrote:
> 1 hour and still the same thing.. One thing different from "normal" is
> that I have 200+ tasks
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 wrote:
> Hello!
>
> I am getting the cold start errors at 80-90
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:0
Hello,
Is this normal? I am using the task queues, I've added about 20 tasks
and all of them returned with a 500 error on the first execution
(indexes being built or cold start latency), and now after 25 minutes
they are all still in queue, is it normal to take that long after an
error? Or is just
Mine happens at pretty random rates too
> - What is your application ID?
footbattle
> - How do you know it is being cycled out? You'll need to insert some code
> that only gets called when the app cold starts.
Random "Request was aborted after waiting too long to attempt to
service your request."
Fabrizio,
I always get these errors right after I deploy a new version of my
app, I don't know if that is the case on yours.
On Jan 15, 9:09 am, John Patterson wrote:
> Can you see long loading requests in your logs? That is requests
> taking over 10 seconds that would be logged immediately
Hello,
>From my tests, it usually takes from 20 minutes to 1 hour until the
new billing settings start working. But I never hit my quota limit,
the closer I got was 90ish% of the limit while waiting for the new
settings (i almost had a heart attack, lol)
On Jan 15, 12:29 pm, Raphael André Bauer
OverQuota.
On Dec 21, 1:23 pm, WSouza wrote:
> Here is the stack:
>
> com.google.apphosting.api.ApiProxy$OverQuotaException: The API call
> datastore_v3.RunQuery() required more quota than is unavailable.
>
> com.google.apphosting.api.ApiProxy$OverQuotaException: The API call
>
Here is the stack:
com.google.apphosting.api.ApiProxy$OverQuotaException: The API call
datastore_v3.RunQuery() required more quota than is unavailable.
com.google.apphosting.api.ApiProxy$OverQuotaException: The API call
datastore_v3.RunQuery() required more quota than is unavailable.
at c
Hello,
I am getting a lot of "Request was aborted" errors today in a cron
job, and the rate is varying a lot, sometimes 10-15% of the requests
are dropped with that error, but with peaks of 80%.
The whole message is "Request was aborted after waiting too long to
attempt to service your request. M
ApiProxy.UnknownException (sometimes)
On Nov 6, 5:22 pm, Diana Cruise wrote:
> There are only 5 exceptions documented for the datastore at the link
> below:
>
> http://code.google.com/appengine/docs/java/javadoc/com/google/appengi...
>
> From the descriptions, it appears only 2 of 5 are conditio
Ok,
I've found out, there is a URL that is the top 1 and it is not showing
on the Current Load Panel.
On Oct 27, 11:59 am, WSouza wrote:
> Hello,
>
> My CPU seconds used/second jumped from an average of 1-1.5 to 5-6
> since 5am (et) this morning, I am trying to find out what i
Is there any better way to update 25 entities (different entity
groups) than doing everything in a single put? It is taking about
500ms plus about 2-3s of CPU time and I have to do that a lot.
--~--~-~--~~~---~--~~
You received this message because you are subscribe
Hello,
My CPU seconds used/second jumped from an average of 1-1.5 to 5-6
since 5am (et) this morning, I am trying to find out what is going on,
but the "% CPU used last hrs" on the dashboard page seems to be
broken, if I add all them up, the total is 20% (I have just a few
URIs, and just 4 with
Hello,
Is it possible to slow down the local datastore? So it matches more
the performance of the appengine? It would be awesome to add a short
delay on each call to the datastore, so the local debugging/profiling
feels more like the production environment.
--~--~-~--~~~--
00 errors. After rolling
> the update back you can try to deploy again.
>
>
>
> On Thu, Oct 22, 2009 at 11:51 AM, WSouza wrote:
>
> > Hello,
>
> > Since about 15 mins ago, when I try to update my application, it is
> > returning an error 500 (internal se
.java:55)
On Oct 22, 12:51 pm, WSouza wrote:
> Hello,
>
> Since about 15 mins ago, when I try to update my application, it is
> returning an error 500 (internal server error) and if i try again,
> error 409 (conflict) until I restart my eclipse, then it goes back to
> error 5
Hello,
Since about 15 mins ago, when I try to update my application, it is
returning an error 500 (internal server error) and if i try again,
error 409 (conflict) until I restart my eclipse, then it goes back to
error 500 once and then 409 again.
Did something happen and my application got locke
Hello,
I am trying to update my application and it shows the following error:
Uploading index definitions.
java.io.IOException: Error posting to URL:
http://appengine.google.com/api/datastore/index/add?app_id=footbattle&version=1&;
500 Internal Server Error
It was working until now, and the dat
21 matches
Mail list logo
