actually, the problem at first was, that the index hadn't been created
at all.
you first need to run as - web application in eclipse.
this will generate the necessary war/WEB-INF/appengine-generated/
datastore-indexes-auto.xml
then deploy to appengine it works
then, as ikai lan stated you might
Nope, I don't think I have that kind of fields.
In my parent entity, 2 properties are indexed : the primary key
(programatically defined based on a String), plus another key (unowned
relationship).
In my child entity, 2 properties as well : the primary key (programatically
defined as well), plus a
I am considering using AppEngine for deploying a webapp which I am
developing. As part of my investigation into the AppEngine platform I
have been checking the response time for simple requests. To this end,
I have written a simple PING servlet:
@SuppressWarnings(serial)
public class Ping extends
Hi mchr,
Check you syslog on app engine dashboard at INFO level: you will very
probably that some of those late queries are due to the fact that App
Engine restarts your application.
At least currently, App Engine tries to swap out apps that are
inactive for some (limited) time. This does not
Thanks for your response.
Is it realistic that Google would terminate an instance which was
handling 1 request a second?
My AppEngine logs suggest that this is not happening. There are no logs
about starting an instance after the very first request.
--
You received this message because you are
Hi,
This is the kind of message you have to look for (from my logs) This
request caused a new process to be started for your application, and
thus caused your application code to be loaded for the first time.
This request may thus take longer and use more CPU than a typical
request for your
I have checked my logs and I only have one instance startup log when I
first starting sending requests to my ping servlet.
Here is some more output from my ongoing test:
EC2:
Thu Nov 25 12:03:57 GMT 2010,300,0,181,298,176,2,860
Thu Nov 25 12:09:22 GMT 2010,300,0,177,299,176,1,537
Thu Nov 25
Hi,
Did you check the lengh of your path (i.e how many router hops)
between your location and App Engine / EC2 datacenter ? That may have
big influence also.
You should be clear about what you measure: the resp time of App
Engine / EC2 ot the length of the path between various locations.
There are actually more hops in the EC2 traceroute!
AppEngine traceroute:
...
7 195.66.224.125 (195.66.224.125) 18.149 ms 17.518 ms 17.366 ms
8 64.233.175.25 (64.233.175.25) 16.686 ms 16.969 ms 17.007 ms
9 72.14.232.134 (72.14.232.134) 22.666 ms 23.988 ms 24.210 ms
10 216.239.46.85
On Nov 18, 7:00 am, Ian Marshall ianmarshall...@gmail.com wrote:
Hi Thufir,
I have looked at the documentation for the plug-in you mention. I had
looked at this before: this seems to me to have little update activity
(and perhaps is supported by one person only).
On a closer look, there
Hi all
--
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 google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
Hi all,
I am using the grails app-engine and jpa-gorm plugin. I wrote a simple
class
User {
@Basic(optional = false)
String emailAddress;
}
I then run grails generate-all com.package.User
I am able to create my user without entering any emailAddress, using
the auto-generated scaffolding page.
12 matches
Mail list logo
