OC, You are sure, after checked at least 3 times, that you are not using an EO from another EOEditingContext in this process?
You may also try to construct a dedicated EOF stack for the process to isolate it completely. Samuel Le 2014-12-11 à 13:54, OC <[email protected]> a écrit : > On 11. 12. 2014, at 14:37, OC <[email protected]> wrote: > >> it was again caused by/reported in a background thread which imports CSV, >> exactly like before -- so it seems highly probable the culprit would be >> _somewhere somehow_ in the concurrent access of the background thread and >> the main one... > > I wonder... is it somewhere documented when exactly WebObjects lock/unlock > the OSC? > > I must be missing something obvious, but to be quite frank, I don't really > get why EOCustomObject.willReadRelationship does unlock the OSC. My > (self-evidently wrong) intuition would say they should either not do anything > with locks in there, or, perhas, they should lock in willRead, not unlock... > > Far as I've been able to find the culprit so far, it looks like > > (a) somewhere in EOEditingContext.saveChanges() the OSC gets locked > (b) in which moment the background task gets to read > EOCustomObject.storedValueForKey for an EO (in its own editing context)... > > ... and that boils down through EOCustomObject.willReadRelationship to unlock > the OSC (without trying to lock it, which would simply sleep the thread). > Which causes the exception. > > Thanks, > OC > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/samuel%40samkar.com > > This email sent to [email protected] _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
