Re: Concurrency Issue
Re: Concurrency Issue
- Subject: Re: Concurrency Issue
- From: Andrew Lindesay <email@hidden>
- Date: Thu, 8 Apr 2010 07:53:58 +1200
Hi Mike;
Good to know "user info" not called within WO and that EOUtilities is not locking; there is one other place in my code where I use the info dictionary on the object store so it must be something of a race condition in my code somehow... I will investigate.
cheers.
> Definitely the underlying cause for the exception, but as far as what triggered this event, that's a tougher one. It doesn't really make sense to me, actually. The only API that actually mutates EOObjectStore's userInfo dict is setUserInfoForKey, which isn't called anywhere in the code. Are you using this method in your own code? All the other accesses of EOObjectStore's userInfo result in copies, so I'm not sure who actually modified the thing underneath you. Definitely there is a locking bug in this code, though. Either it needs to be under the standard objectstore lock (which EOUtilities isn't respecting), or it needs to be synchronized (which it's not).
___
Andrew Lindesay
www.silvereye.co.nz
_______________________________________________
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