Bug 45409

Bug: 45409

Impact:

Product:

GemStone/S 64 Bit

Versions:

3.2.6, 3.2.5, 3.2.4, 3.2.3, 3.2.2, 3.2.1, 3.2, 3.1.0.6, 3.1.0.5, 3.1.0.4, 3.1.0.3, 3.1.0.2, 3.1.0.1, 3.1, 3.0.1, 3.0, 2.4.8, 2.4.7, 2.4.6, 2.4.5.1, 2.4.5, 2.4.4.8, 2.4.4.7, 2.4.x, 2.3.1.6, 2.3.x, 2.2.6.5, 2.2.5.4, 2.2.x, 2.x, 1.x

Platform:

Fixed In:

3.2.7

Object >> isCommitted may return true after failed commit

After a failed commit, temporary objects that would have been committed are in a special state, normally resolved by abort or by a retry of the commit. After the failed commit but before further commit or abort, sending #isCommitted to these temporary objects returns true, which is incorrect since the objects were not actually committed.

Workaround

After a failed commit, application code must resolve the issues in order to either commit successfully or abort (or log out). The code that resolves the commit issues should not rely on the results of isCommitted.