Bug 49448

GemStone/S 64 Bit

3.6, 3.5.5, 3.5.4, 3.5.3, 3.5.1

3.6.1, 3.5.6

GEM_ABORT_MAX_CRS = 0 does not work as documented

The configuration parameter GEM_ABORT_MAX_CRS controls the number of commit records that are analyzed on Gem abort, to compute the write set union. If the number of commit records is higher than this limit, all committed in-memory objects must be re-read.

The documentation says that a value of zero means the setting is "unlimited".  This limit is not being applied; a value of zero is effectively treated as analyze no commit records.

Also, the documentation incorrectly states that this feature applies to Gems that are in transaction. It actually applies on all aborts, regardless if the Gem is in transaction or not.

Workaround

To ensure all commit records are always analyzed, use the maximum value, 2147483647.


Last updated: 3/18/21