You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2013/08/29 08:35:54 UTC
[jira] [Commented] (JCR-3658) MembershipCache not consistently
synchronized
[ https://issues.apache.org/jira/browse/JCR-3658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753367#comment-13753367 ]
Marcel Reutegger commented on JCR-3658:
---------------------------------------
In addition, the cache is too tightly synchronized and does not allow access to the cache when a thread is loading data in case of a cache miss.
> MembershipCache not consistently synchronized
> ---------------------------------------------
>
> Key: JCR-3658
> URL: https://issues.apache.org/jira/browse/JCR-3658
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core, security
> Affects Versions: 2.7
> Reporter: Tobias Bocanegra
> Assignee: Marcel Reutegger
> Priority: Minor
>
> the membership cache access is mostly synchronized on 'this' but in the onEvent() handler, the internal cache object is synchronized.
> suggest: to improve cache access by a r/w lock instead.
--
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