Re: EODatabaseContext.initializeObject(): No snapshot for gid
Re: EODatabaseContext.initializeObject(): No snapshot for gid
- Subject: Re: EODatabaseContext.initializeObject(): No snapshot for gid
- From: Paul Hoadley <email@hidden>
- Date: Thu, 04 Aug 2016 20:33:18 +0930
Hi Maik,On 4 Aug 2016, at 6:16 PM, Musall Maik < email@hidden> wrote:
usually when something like that happened, I ended up violating one of the EOF commandments [1] again. Might be worth to check them every once in a while as a reminder when something strange happens in EOF where you don't have a clue what might have caused it.
Good idea—I’ll comb over the code again.
I also had things like that happen when using autolocking in very high concurrency situations. When the lock/unlock cycle happens too frequently in too many threads simultaneously, all sorts of EOF exceptions can happen. There must be some kind of race condition somewhere deep within. Each and every time I solved it by switching to the lock/try/finally/unlock scheme (you know what I mean?).
How high is “very high”? This app sees (what I’d call) modest concurrency at best. But maybe I’ll see if I can switch over to manual here—yes, I know what you’re describing.
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden