How would proper map sync help here then?
Are you saying there is a put and get going on at the same time?
Imo, this then means WF' dependencies are not done right.
btw: when do you "corrupt" a HashMap? (wrt my diff manifestation)
With multiple concurrent puts/removes, or can it be mixture of puts/gets/removes?
It looks exactly how it would manifest. Something isn't in the map that should be, so an error is thrown.
That's one thing -- dunno how that did pop-up before. ;-)
But I doubt that just non-synchronised collections/maps cause this -- it would manifest differently.
Imo, it must also be a race-condition in WF.