Risk of lost data in RcIdentityBag
When the internal collections of an RcIdentityBag are large, and
a commit conflict invokes the reduced-conflict selective abort
retry logic, it is possible for a modification to an RcIdentityBag
to be lost after a commit that succeeded. This is not a common
problem but can occur in heavily used RcIdentityBags. The
circumstances depend on the particular location in the internal NSC
nodes of the modification and the conflicting session's modification.
Workaround
A special build is available to address this issue.
Last updated: 11/2/07