Nested transactions do not handle abort correctly
Nested transactions, which are logical units of work that are handled locally within an actual GemStone transaction, include abort and commit behavior to manage local state within the nested transaction. The abort operation does not correctly handle large objects, so in some cases the restore of the previous state will not be correct.
You should not use nested transaction in versions affected by this bug.
Last updated: 9/19/14