Replicates not updated by an abort following a failed commit
This bug only applies when logged into a GemStone/S 64 Bit server,
versions 1.0 through 1.1.3 and 2.0.
Following a failed commit in GBS, replicates that have been modified
and have a different value than the corresponding server object are
not resynchronized and will retain the client-modified value.
Workaround:
To ensure all replicates have been re-fetched, log out and log in
again. You can manually stub replicates, but it may be difficult
to ensure you have found all replicates.
Last updated: 5/3/06