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 un
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
(Mike - 20hrs ago)
> random wo tip: iterating keys on NSDictionary = copy, iterating keys on
> HashMap = no copy. if you change dict=>map, beware ConcurrentModExc
^^^ What a co-incidence... probably related issue. I guess there's no easy fix
for this other than lodging a radar.
> I thought I'd
Hello;
I thought I'd ask if anybody else has had any experience with this one?
> java.util.ConcurrentModificationException
> at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793)
> at java.util.HashMap$KeyIterator.next(HashMap.java:828)
> at com.webobjects.foundation.NSDictionary.(N
