You're not going to be able to use Java synchronisation, since you have no guarantee that multiple user requests are even coming into the same JVM.
What's the exact error/exception you're getting? If you're carrying out a lot of updates on the same objects with multiple users, you may need to re-think your persistence design to support this. On Sep 27, 4:54 pm, mscwd01 <mscw...@gmail.com> wrote: > Anyone? > > I have done more searching and cant find anything JDO specific to > handle concurrency so I am assuming it's normal Java locking that'll > need to be implemented? > > On Sep 27, 9:48 am, mscwd01 <mscw...@gmail.com> wrote: > > > > > Hey, > > > My app has been getting a higher number of requests per second > > recently and as a result I've seen an increase in the number of > > concurrent modification exceptions occurring when I persist objects to > > the datastore. The problem arises as I perform a lot of updates on a > > particular object and if two or more people make a request for this > > object at the same time I see the exception. > > > My question is, is there a "proper" way to handle this within JDO > > other than using normal Java synchronization? > > > Thanks!- Hide quoted text - > > - Show quoted text - -- 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. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
