If you are using HRD, this is a well-documented limitation. On Jan 28, 2012, at 12:40 PM, Rémi Bastide wrote:
> Several people have detected a strange behaviour in Google App Engine JDO, > where your app unpredictably returns stale data. > > I've written a small servlet to demonstrate this. > > The code is included in this note, and the app uses the plain vanilla > jdoconfig.xml also included here. > > You can see it live deployed in appengine here > > When using this app, you will notice that occasionally the records that have > just been added or deleted do not show up until a couple of refreshes. > > Things that have been tried but do not appear to work : > Wrapping transactions around adds and deletes > Using cache control headers in response > setting <property name="datanucleus.appengine.datastoreReadConsistency" > value="STRONG" /> in jdoconfig.xml > > I suspect a threading issue that can be solved by configuration options... > > I must be doing something terribly wrong, but I do not see what... > Any help appreciated > > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/3nebSrKk9G4J. > 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?hl=en. > <StaledataServlet.java><jdoconfig.xml> -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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?hl=en.
