We have a simple Java web app - using JPA with 2nd level cache
enabled.
We're running 2 instances of this app simultaneously -- test env and
real production.
Atm the two instances don't diff much; both use the same persistence-
unit name, same cache name, same entities, ...
OK, the application name in the app engine (appengone-
web.xml#application) is of course different.
<persistence-unit name="tb-app">
<provider>org.datanucleus.store.appengine.jpa.DatastorePersistenceProvider</
provider>
<properties>
<property name="datanucleus.NontransactionalRead"
value="true"/>
<property name="datanucleus.NontransactionalWrite"
value="true"/>
<property name="datanucleus.ConnectionURL"
value="appengine"/>
<property
name="datanucleus.appengine.autoCreateDatastoreTxns" value="false"/>
<property name="datanucleus.cache.level2.type"
value="javax.cache"/>
<property name="datanucleus.cache.level2.cacheName"
value="DataNucleus"/>
<property name="datanucleus.cache.query.type"
value="javax.cache"/>
<property name="datanucleus.cache.query.cacheName"
value="DataNucleus-Query"/>
When running our app in production, we sometimes get "phantom" entity
results.
e.g. we see an entity result that matches (is equal to) some result we
put in out test app instance.
Searching for this, let me to this old post:
*
http://stackoverflow.com/questions/3033286/appengine-datastore-phantom-entity-inconsistent-state
which might be similar.
Is this a know issue?
Or are we missing something to do a proper split?
e.g. too much of the "same" stuff -- PU name, cache name, ...?
Thanks for any info.
--
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 [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-java?hl=en.
