Bug 12891

Bug: 12891

Impact:

Critical

Product:

GemStone/S

Versions:

6.7.2.1, 6.7.2, 6.7.1, 6.7, 6.6.5, 6.6.4, 6.6.3.3, 6.6.3.2, 6.6.3, 6.6.2, 6.6.1, 6.6, 6.5.8, 6.5.7.5, 6.5.7, 6.5.6, 6.5.5, 6.5.4, 6.5.2, 6.5.1, 6.5, 6.3.1, 6.3, 6.2.x, 6.2, 6.1.6, 6.1.5, 6.1.x, 6.0.x, 5.1.5.1, 5.1.5, earlier versions

Platform:

All

Fixed In:

Failed commits can give inconsistent view of data

When a commit fails, your view of the repository is updated to include  
changes committed by other users since your transaction began. Your  
own changes are preserved. However, this action can generate a view  
in which different subnodes of a single multi-part object (such as  
an NSC) reflect different temporal views of the repository. Queries  
may return wrong answers, or code may behave strangely.

Workaround

To avoid any of these possible inconsistencies, you should abort   
immediately after a failed commit or false continueTransaction. If you  
want to attempt a recommit after an abort, you must compute all of the  
necessary information before you begin the commit, or you may end up  
trying to commit inconsistent data on the next try.