by any chance was this an EO in a parent editing context that also existed in a 
child editingcontext?

ms

On Mar 25, 2010, at 1:24 PM, Marc Guenther wrote:

> Hi,
> 
> we have switched to WO 5.4.3 (from 5.2.3) several months ago. And since that 
> time, we sporadically experience strange exceptions, mostly 
> NullPointerExceptions deep within EOF, most of which could be traced back to 
> a snapshot mysteriously vanishing.
> 
> I had this in the debugger once, and drilled down to all the snapshots in the 
> EODatabase, and there was one entry missing. Interestingly, this was from an 
> entity which is readonly and cached, and also that entry had to have been 
> there before, otherwise the app wouldn't have gotten to the point where it 
> failed. I checked the DB and the value was there. It is from a table which is 
> only used for lookup and never changes.
> 
> This also happened with other snapshots of regular entitites, and we have 
> never really been able to reproduce it reliably. It seems to happen when lots 
> of ECs are involved, but that's only an assumption.
> 
> Has anyone ever seen something like this? Can this be related to the WO 5.4.3 
> switch? I remember some talk about open bugs in 5.4.3, but haven't been able 
> to find anything substantial about it.
> 
> Btw, no WOnder (yet, sniff)
> 
> Thanks,
> Marc
> 
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/webobjects-dev/mschrag%40mdimension.com
> 
> This email sent to msch...@mdimension.com


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to