[dna-issues] [JBoss JIRA] Commented: (DNA-559) GraphSession cloneImmediate fails to remove existing nodes from cache because of Set ordering variations

[Randall Hauch (JIRA)]

    [ https://jira.jboss.org/jira/browse/DNA-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12496709#action_12496709 ] 

Randall Hauch commented on DNA-559:
-----------------------------------

The fix is relatively simple: check whether a node being purged is below a node that already was purged.

> GraphSession cloneImmediate fails to remove existing nodes from cache because of Set ordering variations
> --------------------------------------------------------------------------------------------------------
>
>                 Key: DNA-559
>                 URL: https://jira.jboss.org/jira/browse/DNA-559
>             Project: DNA
>          Issue Type: Bug
>    Affects Versions: 0.6
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.7
>
>
> GraphSession.cloneImmediate(...) has a parameter that specifies whether any existing nodes should be removed (from the connector), and if this connector request succeeds and did remove those nodes, the method continues by attempting to purge these nodes from the cache.  However, the request collects in a Set the Location for each of the removed nodes, so the order of these nodes cannot be guaranteed.  And in fact when the cloneImmediate method walks them, the test was purging a parent node followed by a child node.  Since purging the parent also purged all children (and other descendants), attempting to purge the child results in an exception.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira