sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SLING-7591) Session leak when a ResourceResolver is created from a Session then gets cloned
Date Tue, 31 Jul 2018 05:54:00 GMT

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

Carsten Ziegeler updated SLING-7591:
------------------------------------
    Fix Version/s:     (was: JCR Resource 3.0.10)
                   JCR Resource 3.0.12

> Session leak when a ResourceResolver is created from a Session then gets cloned
> -------------------------------------------------------------------------------
>
>                 Key: SLING-7591
>                 URL: https://issues.apache.org/jira/browse/SLING-7591
>             Project: Sling
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: JCR Resource 3.0.8
>            Reporter: Csaba Varga
>            Assignee: Carsten Ziegeler
>            Priority: Major
>             Fix For: JCR Resource 3.0.12
>
>
> The following steps will cause a new JCR session to be opened then leaked:
>  # Create a ResourceResolver out of an existing JCR session (using AUTHENTICATION_INFO_SESSION)
>  # Call clone() on the ResourceResolver created in step 1, passing the ResourceResolverFactory.USER_IMPERSONATION
key with a username to impersonate
>  # Close the ResourceResolver created in step 2.
> The expected behavior is that since step 2 opened a new JCR Session in the background,
step 3 should close it. The actual behavior is that the JCR session stays open without an
obvious way to close it, and these leaked sessions can pile up if this sequence is executed
often.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message