[Glass] Help understanding a RcReadSet commit conflict

[Dale Henrichs via Glass]

On 06/16/2016 07:54 AM, Mariano Martinez Peck via Glass wrote:
>
>
> Inspect aFaBackgroundProcess/aSymbolDictionary( 
> #'WriteWrite_minusRcReadSet'->anArray( aDictionary( )), 
> #'commitResult'->#'failure', #'RcReadSet'->anArray( 
> aRcCollisionBucket( aRcKeyValueDictionary( ,........)
> --------------------
> .                -> aSymbolDictionary( 
> #'WriteWrite_minusRcReadSet'->anArray( aDictionary( )), 
> #'commitResult'->#'failure', #'RcReadSet'->anArray( aRcCollisionB...
> ..               -> aFaBackgroundProcess
> (class)@         -> SymbolDictionary
> (oop)@           -> 15059544321
> (committed)@     -> true
> (notTranlogged)@ -> nil
> 1@               -> #'commitResult'->#'failure'
> 2@               -> #'RcReadSet'->anArray( aRcCollisionBucket( 
> aRcKeyValueDictionary( 
> 'siteDB-debris-gemstone'->aFaGemStoneDataStore)), aRcCollisionBucket( 
> aRcK...
> 3@               -> #'Write-Write'->anArray( aDictionary( ))
> 4@               -> #'WriteWrite_minusRcReadSet'->anArray( aDictionary( ))
>
Mariano,

I guess we are both blind:) ... While describing the "problem" to a 
co-worker I noticed that the the Write-Write set is NOT EMPTY :):

   3@               -> #'Write-Write'->anArray( aDictionary( ))

The conflict that you are getting is on the empty dictionary 
(aDictionary( )) ... presumably you are creating an empty Dictionary 
somewhere in shared state and two sessions are trying to update the 
dictionary...

Dale