directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FC-38) Potential issues on synchronized protected elements
Date Mon, 03 Nov 2014 23:30:33 GMT

    [ https://issues.apache.org/jira/browse/FC-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195359#comment-14195359
] 

Emmanuel Lecharny commented on FC-38:
-------------------------------------

I don't have a deadlock when running the tests, but my config is different.

Removing the test for nullity put us on a potential trouble, as we have released the readLock
before acquiring the writeLock, thus anotehr thread might perfectly have loaded the graph
in between. Reloading it might cause issues.


> Potential issues on synchronized protected elements
> ---------------------------------------------------
>
>                 Key: FC-38
>                 URL: https://issues.apache.org/jira/browse/FC-38
>             Project: FORTRESS-CORE
>          Issue Type: Bug
>    Affects Versions: 1.0.0-RC39
>            Reporter: Emmanuel Lecharny
>            Priority: Critical
>             Fix For: 1.0.0-RC40
>
>
> There are some classes where we protect a field with a synchronized in order to avoid
concurrent modifications. That's ok, except that one should not access the field while it's
being updated. There are a few cases where it's done, and this should be fixed. 
> The way to do it is to use ReentrantReadWriteLock for that : it allows concurrent reads,
unless a write lock is taken. Writes will block other writes and all the reads until it's
done. 
> The OrgUnitP and PolicyP are protecting sets while updating it that aren't protected
when read (this is fixed for OrgUnitP)
> The AdminRoleUtil, HierUtil, PsoUtil, UsoUtil are all manipulating a graph object which
is synchronized on update, but not on read. This is probably more complex to fix than for
the OrgUnitP/PolicyP classes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message