[jira] [Resolved] (ARIES-968) Consider using a "multiple attempts" strategy versus the current locking strategy when updating sharing policies.

["John Ross (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARIES-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Ross resolved ARIES-968.
-----------------------------

    Resolution: Fixed

Fixed in http://svn.apache.org/viewvc?view=revision&revision=1414804.
                
> Consider using a "multiple attempts" strategy versus the current locking strategy when updating sharing policies.
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: ARIES-968
>                 URL: https://issues.apache.org/jira/browse/ARIES-968
>             Project: Aries
>          Issue Type: Improvement
>          Components: Subsystem
>            Reporter: John Ross
>            Assignee: John Ross
>
> The AriesSubsystem.addRequirements(Collection<Requirement>) method adds the specified requirements to a subsystem's sharing policy, which is controlled by a Region in the RegionDigraph API. Updating a region digraph is atomic. This means a copy of the current digraph is made, updated, and then set in the digraph service. If something else sets a a different copy between the time the first copy is made and set, an exception occurs. Currently, this is mitigated by locking on the SubsystemImpl class. A better mitigating approach would be to make multiple attempts until it either succeeded or some threshold number of attempts was surpassed. This would avoid the bottleneck as well as address the possibility of something outside subsystems interfering.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira