Bug 49715

GemStone/S 64 Bit

3.6.5, 3.6.4, 3.6.3, 3.6.2, 3.6.1, 3.6, 3.5.6, 3.5.5, 3.5.4, 3.5.3, 3.5.2, 3.5.1, 3.5

3.6.2

Risk of Gem writing an invalid tranlog record

It is possible for a Gem to create a BEGIN_DATA tranlog record, with the tranlog record kind field incorrectly set to type 0.

The resulting tranlog containing this invalid record, will error when restored with
    readRecord: unhandled recordKind 0

Workaround

The cause of the incorrect tranlog record kind field is unknown.

In versions with the fix, if the Gem passes an invalid tranlog records to the Stone, the Stone will terminate the Gem and not write the tranlog record, to ensure the tranlogs are not corrupted.


Last updated: 11/9/21