I recently ran into an error when trying to log onto ODK Aggregate,
and found that it was because somehow my quote was maxed out even
though I had only performed a few operations. Today I found this error
in the log:
2011-11-07 23:59:27.761 /gae/watchdog?checkIntervalMilliseconds=180000
500 5430ms 0kb AppEngine-Google; (+http://code.google.com/appengine)
E 2011-11-07 23:59:27.750
org.springframework.web.context.ContextLoader
initWebApplicationContext: Context initialization failed
org.springframework.beans.factory.BeanCreationE
C 2011-11-07 23:59:27.755 Uncaught exception from servlet
javax.servlet.UnavailableException: Initialization failed. at
com.google.apphosting.runtime.jetty.AppVersionHandlerMa
/gae/watchdog has 185 requests in the last 10 hours, and from what I
can tell (then again, I'm new to this and could be very wrong), it
looks like it's eating up my "Datastore Read Operations" quote, which
is why I couldn't log on (this is the current state): Datastore Read
Operations 96% 0.05 of 0.05 Million Ops
I hope to have a 1.0.1 that should at least cap the watchdog when it starts
to fail, but that won't resolve the underlying problem.
There are an excessive number of reads counted against the GAE datastore
causing that limit to be exceeded very easily.
Investigating...
Mitch
···
On Tue, Nov 8, 2011 at 10:07 AM, Anika wrote:
Hi all,
I recently ran into an error when trying to log onto ODK Aggregate,
and found that it was because somehow my quote was maxed out even
though I had only performed a few operations. Today I found this error
in the log:
2011-11-07 23:59:27.761 /gae/watchdog?checkIntervalMilliseconds=180000
500 5430ms 0kb AppEngine-Google; (+http://code.google.com/appengine)
E 2011-11-07 23:59:27.750
org.springframework.web.context.ContextLoader
initWebApplicationContext: Context initialization failed
org.springframework.beans.factory.BeanCreationE
C 2011-11-07 23:59:27.755 Uncaught exception from servlet
javax.servlet.UnavailableException: Initialization failed. at
com.google.apphosting.runtime.jetty.AppVersionHandlerMa
/gae/watchdog has 185 requests in the last 10 hours, and from what I
can tell (then again, I'm new to this and could be very wrong), it
looks like it's eating up my "Datastore Read Operations" quote, which
is why I couldn't log on (this is the current state): Datastore Read
Operations 96% 0.05 of 0.05 Million Ops
I recently ran into an error when trying to log onto ODK Aggregate,
and found that it was because somehow my quote was maxed out even
though I had only performed a few operations. Today I found this error
in the log:
2011-11-07 23:59:27.761 /gae/watchdog?checkIntervalMilliseconds=180000
500 5430ms 0kb AppEngine-Google; (+http://code.google.com/appengine)
E 2011-11-07 23:59:27.750
org.springframework.web.context.ContextLoader
initWebApplicationContext: Context initialization failed
org.springframework.beans.factory.BeanCreationE
C 2011-11-07 23:59:27.755 Uncaught exception from servlet
javax.servlet.UnavailableException: Initialization failed. at
com.google.apphosting.runtime.jetty.AppVersionHandlerMa
/gae/watchdog has 185 requests in the last 10 hours, and from what I
can tell (then again, I'm new to this and could be very wrong), it
looks like it's eating up my "Datastore Read Operations" quote, which
is why I couldn't log on (this is the current state): Datastore Read
Operations 96% 0.05 of 0.05 Million Ops
Just wanted to follow-up about the error - I'm still getting a really
large number of requests from /gae/watchdog (146 requests in the last
8 hours and am already at 68% for datastore read). Is there a way to
stop it altogether? (Again, I'm new to this and not sure if that's
possible, just wondering.)
Thanks again!
···
On 8 nov, 15:11, anikavi...@gmail.com wrote:
> Great! Thanks for your help, Mitch.
No. I'm working on 1.0.1 and aim to get it out today. Upgrading to it
should help.
Mitch
···
On Thu, Nov 10, 2011 at 7:49 AM, Anika wrote:
Hi Mitch,
Just wanted to follow-up about the error - I'm still getting a really
large number of requests from /gae/watchdog (146 requests in the last
8 hours and am already at 68% for datastore read). Is there a way to
stop it altogether? (Again, I'm new to this and not sure if that's
possible, just wondering.)