jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Olaf Märker (JIRA) <j...@apache.org>
Subject [jira] [Updated] (JCR-3683) Synchronisation of nodes in cluster does not invalidate label cache
Date Fri, 18 Oct 2013 08:44:42 GMT

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

Olaf Märker updated JCR-3683:
-----------------------------

    Status: Patch Available  (was: Open)

I added a patch that solved the issue for me.

> Synchronisation of nodes in cluster does not invalidate label cache
> -------------------------------------------------------------------
>
>                 Key: JCR-3683
>                 URL: https://issues.apache.org/jira/browse/JCR-3683
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: clustering
>    Affects Versions: 2.2.13
>            Reporter: Olaf Märker
>              Labels: clustering, labels, synchronization
>         Attachments: jackrabbit-core-JCR-3683.patch
>
>
> When I set or remove a label to/from a version of a node on one cluster node and after
the sync delay has passed I read the node versions on another cluster node, then I got the
old label settings.
> While debugging I saw, that the label change event  was processed on all cluster nodes,
the method InternalVersionManagerImpl.externalUpdate() was called but the label cache of the
version nodes was not updated.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message