(JDOQuery.java:252) at
Environment: SDK 1.3.4
JUnit = 4
Is there a code sample we can use as reference?, with all of the
required JAR files?. I haven't been able to run a single test that
requires accessing datastore.
On Jun 30, 5:58 pm, luijar luis.j.aten...@gmail.com wrote:
I am seeing this however
We just experienced an outtage that seems to be from Google App Engine
for one of our registered app ID's. It lasted for several hours and it
seems to be back up again without us making any changes. Has anyone
else experienced this? If so, what was the cause?
--
You received this message because
8:55AM Pacific was the last error we saw. Basically, it was throwing
DeadlineExceededExceptions quickly all of the time.
On Apr 27, 12:11 pm, luijar luis.j.aten...@gmail.com wrote:
We just experienced an outtage that seems to be from Google App Engine
for one of our registered app ID's
Thanks Toby,
Can you point me to the threads you talk about?
Thanks,
Luijar
On Mar 2, 4:15 am, Toby toby.ro...@gmail.com wrote:
Hi luijar,
I had the same problem -but no time-out- and I got some better
performance by removing all autowire and annotation-scan stuff and
also by putting
) is that I am also using
Spring AOP, which I suspect adds a lot of overhead to the mix.
On Mar 3, 5:18 pm, luijar luis.j.aten...@gmail.com wrote:
Thanks Toby,
Can you point me to the threads you talk about?
Thanks,
Luijar
On Mar 2, 4:15 am, Toby toby.ro...@gmail.com wrote:
Hi luijar
Thanks for the advice, I'll try that.
On Mar 1, 2:31 pm, Rusty Wright rwright.li...@gmail.com wrote:
Try using the old way with xml configuration for wiring your beans together.
The word on the street is that Spring's component scanning takes a lot of
time.
luijar wrote:
Nope, I am
if your
issue was resolved or reduced by using the above fix.
On Feb 20, 12:05 am, luijar luis.j.aten...@gmail.com wrote:
I believe my development environment was on 1.3.0. That might be
something to look at, although it seems that probably it's a very
small overhead, do you have any
is that the initialization of your app takes longer than 30
seconds.
Pinging your app doesn't help when the app is restarted due to
redeployment
or maintenance, or when high traffic demands a second instance.
You should try to reduce your startup time.
regards,
Stephan
2010/2/17 luijar
is that you need to keep your app alive by simulating activity
on it. Or go the non Spring route.
Thanks
On Feb 16, 4:14 pm, luijar luis.j.aten...@gmail.com wrote:
Hello Google App Engine forum,
We have been seeing ever since we deployed our applications
(currently 3 of them) that when our
Hello Google App Engine forum,
We have been seeing ever since we deployed our applications
(currently 3 of them) that when our application instances become idle
(they have not been hit for x amount of seconds) subsequent requests
return with a 500 response. Logs show a hard deadline exceeded
I am beginning to see this problem when uploading my application to
the AppEngine. Here is the stack trace:
com.google.appengine.tools.admin.AdminException: Unable to update app:
Error writing to server
at com.google.appengine.tools.admin.AppAdminImpl.update
(AppAdminImpl.java:62)
at
11 matches
Mail list logo
