Hi, Thanks for your advise. What do you mean on deploying again? I was getting this error when running my app locally and when I tried running JUnit Tests on it.
Adam On Apr 26, 6:04 am, branflake2267 <branflake2...@gmail.com> wrote: > I got an error like this too on upgrading, but I changed the version > and deployed again. My project worked after that. > > Not sure if this would fix it, but worth a try. > > Brandon Donnelsonhttp://gwt-examples.googlecode.com > > On Apr 10, 3:27 pm, AdamM <mautner.a...@gmail.com> wrote: > > > > > Hi, > > > I am developing an application, that operates on multiple entity > > groups in multiple datastore transactions. > > > I first create a PersistenceManager and open a transaction on it.I > > make an object persistent using this transaction, but I do not commit > > it. After this I create a new PersistenceManager with a transaction > > from the same factory, I make persistent an object to a different > > entity group. Again I do not commit. At the end I will commit the > > transaction after each other. > > > There is a foreign key relationship between the 2 objects (I store the > > Object with primary key first). > > > The second transaction fails to commit with an Exception: > > > NestedThrowablesStackTrace: > > java.lang.IllegalStateException: Attempted to deregister a transaction > > that is not currently registered. > > at > > com.google.appengine.api.datastore.TransactionStackImpl.remove(TransactionS > > tackImpl.java: > > 61) > > at > > com.google.appengine.api.datastore.TransactionImpl.commit(TransactionImpl.j > > ava: > > 71) > > at > > org.datanucleus.store.appengine.DatastoreTransaction.commit(DatastoreTransa > > ction.java: > > 61) > > at > > org.datanucleus.store.appengine.DatastoreXAResource.commit(DatastoreXAResou > > rce.java: > > 88) > > (I do not get this error, if I leave the persistence of the object out > > from the 2nd transaction.) > > > I was running this code both from JUnit Tests and on Local App Engine > > instance. > > > This was working with 1.2.6 or 1.3.0 but not with 1.3.2. > > > I also have a JUnit Test to test concurrent modification, I used to > > get JDOCanRetryException on concurrent changes, but now with the new > > version I am getting: > > > java.util.ConcurrentModificationException: too much contention on > > these datastore entities. please try again. > > at > > com.google.appengine.api.datastore.DatastoreApiHelper.translateError(Datast > > oreApiHelper.java: > > 37) > > at > > com.google.appengine.api.datastore.DatastoreApiHelper.makeSyncCall(Datastor > > eApiHelper.java: > > 63) > > at > > com.google.appengine.api.datastore.TransactionImpl.makeSyncCall(Transaction > > Impl.java: > > 42) > > at > > com.google.appengine.api.datastore.TransactionImpl.makeSyncCall(Transaction > > Impl.java: > > 56) > > at > > com.google.appengine.api.datastore.TransactionImpl.commit(TransactionImpl.j > > ava: > > 66) > > > Has anything changed in 1.3.2? > > > Please help. > > > Regards, > > > Adam > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appeng...@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group > athttp://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
