Hi Len, "attempted to deregister a transaction that is not currently registered" is an error thrown by the datastore api when a call is made to commit a txn and there is no txn to commit. Is it possible you have some path through your code that would result in calling commit() more than once or calling commit() after a rollback()?
I can't explain the partial data you're seeing - transactional writes are atomic from your app down to the datastore down to the storage layer that the datastore is built on. Since you had 2 cron jobs executing concurrently is it possible that the writes interacted with one another in some previously unforeseen way? Max On Tue, Dec 8, 2009 at 1:14 AM, lent <[email protected]> wrote: > I took a look at the log entries more closely and it looks like the > cron job which is to run daily got kicked off twice for some reason. > Instead of one chain of 500 sequential tasks being started up two > chains of 500 were running in parallel. This may explain the errors I > was getting though I don't understand how there seems to have been a > partial update. > > Len > > On Dec 8, 12:35 am, lent <[email protected]> wrote: > > Hello, > > > > I have a daily cron job which kicks off a sequential 500 tasks > > (chained). These usually run successfuly but a few days ago, on the > > first task, I got the following error: > > > > [xxxxxxxxxxx/1.338222621935386721].<stderr>: > > java.lang.IllegalStateException: Attempted to deregister a transaction > > that is not currently registered. > > > > On the next task, I got the error again: > > > > [xxxxxxxxxxx/1.338222621935386721].<stderr>: > > java.lang.IllegalStateException: Attempted to deregister a transaction > > that is not currently registered. > > > > Then on the remaining 498 tasks I got the error: > > > > com.jostleme.jostle.ui.web.controller.DriverController > > processRefreshContributorTagsTask: failure while updating refresh tags > > info. Cause: Transaction rolled back due to failure during commit; > > nested exception is javax.persistence.PersistenceException: > > Transaction rolled back due to failure during commit > > > > After this data seems to have gotten corrupted. By this I mean that > > something that should have run in a transaction (all or nothing) seems > > to have done a partial update. > > > > Does anyone (especially google folks) have any insights on this > > behavior? > > > > Regards, > > Len > > -- > > 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]<google-appengine-java%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > > -- 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.
