Re: Vs: Re: Vs: Re: Vs: Re: [appengine-java] Should JDO use be synchronized in threadsafe=true application?
Ok. My change to PMF.java to synchronize the get of the PersistenceManager did NOT correct the problem. Going to fallback to synchronizing every usage of the PersistenceManager (reads and writes). Will update this issue with any further results. On May 17, 1:54 am, Stephen Johnson wrote: > Ah, I missed the point about it being tasks and didn't realize the > threadsafe only applied to user requests and not tasks. If indeed that was > the case. > > > > On Mon, May 16, 2011 at 10:44 PM, Juha K wrote: > > The datanucleus issue has a comment "Then, when my tasks run in parallel, > > initialisation has already been done and the problem doesn't appear any > > more.", so before the threadsafe property, only tasks were run in parallel. > > Probably that's why I didn't see this error before, I didn't have tasks > > doing db access. > > > -- > > 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-java@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. -- 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-java@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.
Re: Vs: Re: Vs: Re: Vs: Re: [appengine-java] Should JDO use be synchronized in threadsafe=true application?
Ah, I missed the point about it being tasks and didn't realize the threadsafe only applied to user requests and not tasks. If indeed that was the case. On Mon, May 16, 2011 at 10:44 PM, Juha K wrote: > The datanucleus issue has a comment "Then, when my tasks run in parallel, > initialisation has already been done and the problem doesn't appear any > more.", so before the threadsafe property, only tasks were run in parallel. > Probably that's why I didn't see this error before, I didn't have tasks > doing db access. > > -- > 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-java@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. > -- 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-java@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.
Vs: Re: Vs: Re: Vs: Re: [appengine-java] Should JDO use be synchronized in threadsafe=true application?
The datanucleus issue has a comment "Then, when my tasks run in parallel, initialisation has already been done and the problem doesn't appear any more.", so before the threadsafe property, only tasks were run in parallel. Probably that's why I didn't see this error before, I didn't have tasks doing db access. -- 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-java@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.
