Primitive failure when unstubbing for mapped classes of different sizes
If an application uses automatic name-matching class mapping for a subclass of OrderedCollection, and theses OrderedCollection subclasses have unmatched named instance variables, unstubbing of instance with fewer unnamed instance variables can fail.
The problem is when the class on the client more named instance variables than the class with the same name on the server, and a stub is created for an instance with fewer elements than number of instance variables, before the classes are mapped. The attempt to change the class of the stub fails since the stub is too small to accommodate the named instance variables.
Workaround
If you hit this scenario, you should log out of GemStone.
Last updated: 6/19/19