Apache Jackrabbit developers list

Julian Reschke (JIRA | 15 Jun 2012 18:02

Picon

[Created] (JCR-3345) ACL evaluation may return non-fresh results

Julian Reschke created JCR-3345:
-----------------------------------

             Summary: 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.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

(Continue reading)

Julian Reschke (JIRA | 15 Jun 2012 18:02

Picon

[Updated] (JCR-3345) ACL evaluation may return non-fresh results


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

Julian Reschke updated JCR-3345:
--------------------------------

    Attachment: JCR-3345.test.patch

> 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.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.

(Continue reading)

angela (JIRA | 15 Jun 2012 18:19

Picon

[Commented] (JCR-3345) ACL evaluation may return non-fresh results


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

angela commented on JCR-3345:
-----------------------------

> in particular not to the session that caused them

i don't think that this is the case. the editing session most probably sees the modified ACL content but the
effective acl such as obtained from the system-session associated with the ac-provider seems not to see
the changes at that point. i could even live with that as long as we could be sure that there were no outdated
entries stored in the cache that were properly updated afterwards. but if it turned out that the the
entrycollector got informed about ac modifications before (-> clearing) and the system session was
reading outdated information on the next permission-eval, that was troublesome.

> 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.test.patch
>
>

(Continue reading)

angela (JIRA | 15 Jun 2012 18:21

Picon

[Comment Edited] (JCR-3345) ACL evaluation may return non-fresh results


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

angela edited comment on JCR-3345 at 6/15/12 4:20 PM:
------------------------------------------------------

> in particular not to the session that caused them

i don't think that this is the case. the editing session most probably sees the modified ACL content but the
effective acl such as obtained from the system-session associated with the ac-provider seems not to see
the changes at that point. i could even live with that as long as we could be sure that there were no outdated
entries stored in the cache that were properly updated afterwards. but if it turned out that the the
entrycollector got informed about ac modifications before (-> clearing) and the system session was
(still) reading outdated information on the next permission-eval, that was troublesome.

      was (Author: anchela):
    > in particular not to the session that caused them

i don't think that this is the case. the editing session most probably sees the modified ACL content but the
effective acl such as obtained from the system-session associated with the ac-provider seems not to see
the changes at that point. i could even live with that as long as we could be sure that there were no outdated
entries stored in the cache that were properly updated afterwards. but if it turned out that the the
entrycollector got informed about ac modifications before (-> clearing) and the system session was
reading outdated information on the next permission-eval, that was troublesome.

> ACL evaluation may return non-fresh results
> -------------------------------------------
>

(Continue reading)

Julian Reschke (JIRA | 19 Jun 2012 17:07

Picon

[Commented] (JCR-3345) ACL evaluation may return non-fresh results


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

Julian Reschke commented on JCR-3345:
-------------------------------------

Odd: tried to modify EntryCollector.collectEntries to refresh:

    protected List<AccessControlEntry> collectEntries(NodeImpl node, EntryFilter filter) throws
RepositoryException {
        LinkedList<AccessControlEntry> userAces = new LinkedList<AccessControlEntry>();
        LinkedList<AccessControlEntry> groupAces = new LinkedList<AccessControlEntry>();

        if (node == null) {
            // repository level permissions
            NodeImpl root = (NodeImpl) systemSession.getRootNode();
            if (ACLProvider.isRepoAccessControlled(root)) {
                NodeImpl aclNode = root.getNode(N_REPO_POLICY);
                filterEntries(filter, new ACLTemplate(aclNode).getEntries(), userAces, groupAces);
            }
        } else {
            node.getSession().refresh(true); ///////////////////// TEST

            filterEntries(filter, getEntries(node).getACEs(), userAces, groupAces);
            NodeId next = node.getParentId();
            while (next != null) {
                Entries entries = getEntries(next);
                filterEntries(filter, entries.getACEs(), userAces, groupAces);

(Continue reading)

Marcel Reutegger (JIRA | 20 Jun 2012 17:35

Picon

[Commented] (JCR-3345) ACL evaluation may return non-fresh results


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

Marcel Reutegger commented on JCR-3345:
---------------------------------------

This is related to JCR-2813, which set to fixed, but apparently it still happens. I can see the WARN message
in the logs when I run the test:

WARN  [main] ItemStateReferenceCache.java:176  overwriting cached entry e8248005-46cb-445f-aa13-a4b0bc8f3a65

Debugging the system session shows that the aclNode (with UUID e8248005-46cb-445f-aa13-a4b0bc8f3a65
in my test run) refers to a NodeState that has an overlayed state, which is not up-to-date. It is missing an
access control entry child node that was added in the test. Further analyzing the cache of the
SharedItemStateManager shows that the NodeState for aclNode in there in fact has the correct number of
child nodes.

> 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.test.patch

(Continue reading)

Julian Reschke (JIRA | 20 Jun 2012 18:12

Picon

[Commented] (JCR-3345) ACL evaluation may return non-fresh results


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

Julian Reschke commented on JCR-3345:
-------------------------------------

Marcel: thanks a lot.

I just checked and can confirm that every time a test case fails for a given node, the warning was generated
for one of it's child nodes.

                
> 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.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

(Continue reading)

Julian Reschke (JIRA | 20 Jun 2012 18:14

Picon

[Commented] (JCR-3345) ACL evaluation may return non-fresh results


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

Julian Reschke commented on JCR-3345:
-------------------------------------

For the record: the problem is not related to the CachingEntryCollector; the problem also occurs when no
caching takes place at all.

> 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.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.

(Continue reading)

Marcel Reutegger (JIRA | 21 Jun 2012 09:12

Picon

[Updated] (JCR-3345) ACL evaluation may return non-fresh results


     [
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 profile.

> 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
>
>

(Continue reading)

Marcel Reutegger (JIRA | 21 Jun 2012 11:09

Picon

[Commented] (JCR-3345) ACL evaluation may return non-fresh results


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

Marcel Reutegger commented on JCR-3345:
---------------------------------------

Tests also pass with integrationTesting profile.

> 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

(Continue reading)

angela (JIRA | 21 Jun 2012 11:30

Picon

[Commented] (JCR-3345) ACL evaluation may return non-fresh results


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

angela commented on JCR-3345:
-----------------------------

marcel, what about the performance tests?

> 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

(Continue reading)

Julian Reschke (JIRA | 21 Jun 2012 13:48

Picon

[Commented] (JCR-3345) ACL evaluation may return non-fresh results


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

Julian Reschke commented on JCR-3345:
-------------------------------------

Fixes the problem for me; I would recommend to apply this to trunk, including the change to the test case.

> 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

(Continue reading)

Marcel Reutegger (JIRA | 25 Jun 2012 14:44

Picon

[Updated] (JCR-3345) ACL evaluation may return non-fresh results


     [
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-pre-populate-cache.patch

Here's an alternative approach, which should not increase the risk of deadlocks.

All tests pass with integrationTesting profile enabled.

> 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-pre-populate-cache.patch, 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.

(Continue reading)

Marcel Reutegger (JIRA | 25 Jun 2012 14:46

Picon

[Commented] (JCR-3345) ACL evaluation may return non-fresh results


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

Marcel Reutegger commented on JCR-3345:
---------------------------------------

bq. marcel, what about the performance tests? 

I didn't run those tests because I was rather focusing on why the tests fail with those additional sessions
reading from the workspace.

> 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-pre-populate-cache.patch, 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.

(Continue reading)

angela (JIRA | 25 Jun 2012 15:43

Picon

[Commented] (JCR-3345) ACL evaluation may return non-fresh results


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

angela commented on JCR-3345:
-----------------------------

> I didn't run those tests because I was rather focusing on why the tests fail with those additional sessions
reading from the workspace. 

i see... but i feel that we need to take the performance into account as the issues was basically showing up
while working on an performance issue. so, if you could run some performance tests to prove that it doesn't
have a negative impact would be perfect.

> 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-pre-populate-cache.patch, 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.

(Continue reading)

Marcel Reutegger (JIRA | 2 Jul 2012 13:53

Picon

[Updated] (JCR-3345) ACL evaluation may return non-fresh results


     [
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-pre-populate-cache.patch

This is a modified version of the previous patch. The patch does not change the the way how the cache is
updated in SharedItemStateManager.stateCreated(), which I consider risky in the initial patch.
Instead, the ItemStateReferenceCache now only logs a warning when an item is overwritten, which is not
the same object. With the corresponding change in SharedItemStateManager.Update.end() this now
happens on a regular basis, but is considered OK in the cache.

> 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-pre-populate-cache.patch, JCR-3345-pre-populate-cache.patch,
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

(Continue reading)

Marcel Reutegger (JIRA | 2 Jul 2012 15:37

Picon

[Commented] (JCR-3345) ACL evaluation may return non-fresh results


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

Marcel Reutegger commented on JCR-3345:
---------------------------------------

regarding performance tests:

The test ConcurrentReadAccessControlledTreeTest shows roughly the same numbers with and without the
patch. This is reasonable, since the patch touches only code that is executed when something is changed in
the repository.

In addition I also ran ConcurrentReadWriteTest, which shows comparable numbers. Though the variation in
the timing is quite high (even before the patch) and makes it difficult to tell is there's an impact.

                
> 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-pre-populate-cache.patch, JCR-3345-pre-populate-cache.patch,
JCR-3345.patch, JCR-3345.test.patch

(Continue reading)

Julian Reschke (JIRA | 2 Jul 2012 18:57

Picon

[Commented] (JCR-3345) ACL evaluation may return non-fresh results


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

Julian Reschke commented on JCR-3345:
-------------------------------------

Works for me (in that the initial problem is gone, and all tests continue to pass). That being said, I don't
have sufficient insight about whether this is the right thing to do.

> 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-pre-populate-cache.patch, JCR-3345-pre-populate-cache.patch,
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.

(Continue reading)

Marcel Reutegger (JIRA | 4 Jul 2012 15:48

Picon

[Resolved] (JCR-3345) ACL evaluation may return non-fresh results


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

Marcel Reutegger resolved JCR-3345.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.5.1

Applied most recent patch in revision: 1357265

> 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
>             Fix For: 2.5.1
>
>         Attachments: JCR-3345-pre-populate-cache.patch, JCR-3345-pre-populate-cache.patch,
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.

(Continue reading)

Return

Return to gmane.comp.apache.jackrabbit.devel.

Project Web Page

Apache Jackrabbit developers list

Search Archive

Language

Change language

Options

Current view: Threads only / Showing only 20 lines / Not hiding cited text.
Change to All messages, whole messages, or hide cited text.

Post a message
NNTP Newsgroup
Classic Gmane web interface
XML

XML

RSS Feed
List Information

About Gmane