IdentityBag adds in nested transactions may not be tranlogged correctly
If additions are made to an IdentityBag or a subclass of IdentityBag within a nested transaction, the additions may not be logged correctly in the transaction logs.
If the database is later restored from backup and the transaction logs replayed, or on automatic recovery after an unclean shutown, these added elements will be missing, and the variable that tracks the size of the collection will be incorrect.
Workaround
The fix is in the C code. Due to related bugs, you should upgrade to GemStone v3.6.2 or later, or v3.5.8 or later.
Last updated: 9/25/20