jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCR-3345) ACL evaluation may return non-fresh results
Date Thu, 21 Jun 2012 07:12:42 GMT

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

Marcel Reutegger updated JCR-3345:

    Attachment: JCR-3345.patch

Here's a patch the uses the currentlyLoading set to gard newly created items from being loaded
concurrently by other sessions.

I'm not able to reproduce the test failures anymore with this change, but I fear it might
introduce a deadlock. So, consider this work in progress.

All jackrabbit-core tests pass and I'm currently running them again with the integrationTesting
> ACL evaluation may return non-fresh results
> -------------------------------------------
>                 Key: JCR-3345
>                 URL: https://issues.apache.org/jira/browse/JCR-3345
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core, security
>    Affects Versions: 2.6
>            Reporter: Julian Reschke
>         Attachments: JCR-3345.patch, JCR-3345.test.patch
> It appears that changes to access control entries are not always visible right away;
in particular not to the session that caused them.
> EntryCollectorTest has recently been extended to run the existing set of tests under
load as well, and occasionally we see tests failing because of ACEs not yet being returned.
> Increasing the load (see attached patch for the test) seems to make it easier to reproduce.
> The underlying reason might be that this involves multiple sessions to be in sync.
> Note that the cache in CachingEntryCollector doesn't seem to be the cause; disabling
it by commenting out all write operations to the cache (making everything a cache miss) doesn't
change the outcome.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message