You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2015/01/30 08:17:34 UTC

[jira] [Commented] (SLING-3859) ResourceResolver from JcrItemAdapterFactory is not closed

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

Felix Meschberger commented on SLING-3859:
------------------------------------------

linking to removal issue. Also discussed on dev@ [Removing or at least deprecating JcrItemAdapterFactory|http://sling.markmail.org/thread/xl65subaedx4kluh]

> ResourceResolver from JcrItemAdapterFactory is not closed
> ---------------------------------------------------------
>
>                 Key: SLING-3859
>                 URL: https://issues.apache.org/jira/browse/SLING-3859
>             Project: Sling
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: JCR Resource 2.3.6
>            Reporter: Carsten Ziegeler
>             Fix For: JCR Resource 2.4.2
>
>
> Whenever a node or property is adapted to something a new resource resolver is created with the same user session as the node is from. However, this resolver is never closed and therefore is a potential memory leak



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