Bug 40454

Critical

GemStone/S 64 Bit

2.4.1, 2.4, 2.3.1.6, 2.3.1, 2.3, 2.2.5.4, 2.2.5.3, 2.2.5.2, 2.2.5.1, 2.2.5, 2.2.x, 2.2, 2.1.4, 2.1.x, 2.1, 2.0.x, 2.0

All

2.4.2

Failed commit has small risk of losing data

If a failed commit is not immediately followed by an abort, there is a
pathway through the code where a newly created object may not be written
out to the repository.  This results in object does not exist errors, and
if the OOP is re-used, logical corruption.

This bug is in GCI code so affects GBS applications.  While conditions
for this bug include modifications to objects to refer to newly created
objects, commit failure, and later successful commit, there are other conditions
required; this bug appears to be rare and difficult to reproduce.

Workaround

Ensure that all commit failures are followed immediately by abort.


Last updated: 1/18/10