jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Parvulescu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-2875) Namespaces keep references to old node states
Date Mon, 03 Aug 2015 09:13:05 GMT

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

Alex Parvulescu commented on OAK-2875:
--------------------------------------

bq. is refreshing the name spaces spec. compliant?
right, this should be the main concern to driving this patch forward.

as discussed with [~mduerig] offline, this may hold the key to the spec compliance [0]:
{code}
3.5.1 Namespace Registry

The local namespace mapping of a session is determined by the initial set of mappings copied
from the namespace registry and any session-local changes made to that set.
{code}

So really the question is when is it legal to refresh the mappings, if ever?
The patch I'm proposing would change the behavior from never refreshing to refreshing on session
refresh.

[0] http://www.day.com/specs/jcr/2.0/3_Repository_Model.html#3.5.1%20Namespace%20Registry

> Namespaces keep references to old node states
> ---------------------------------------------
>
>                 Key: OAK-2875
>                 URL: https://issues.apache.org/jira/browse/OAK-2875
>             Project: Jackrabbit Oak
>          Issue Type: Sub-task
>          Components: core, jcr
>            Reporter: Alex Parvulescu
>            Assignee: Alex Parvulescu
>             Fix For: 1.3.5
>
>         Attachments: OAK-2875-v1.patch, OAK-2875-v2.patch
>
>
> As described on the parent issue OA2849, the session namespaces keep a reference to a
Tree instance which will make GC inefficient.



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

Mime
View raw message