[jira] Assigned: (SLING-488) Pooled sessions are not reused when workspace is null

["Felix Meschberger (JIRA)" <ji...@apache.org>]

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

Felix Meschberger reassigned SLING-488:
---------------------------------------

    Assignee: Felix Meschberger

> Pooled sessions are not reused when workspace is null
> -----------------------------------------------------
>
>                 Key: SLING-488
>                 URL: https://issues.apache.org/jira/browse/SLING-488
>             Project: Sling
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: 2.0.0
>            Reporter: Dominique Pfister
>            Assignee: Felix Meschberger
>
> I noticed this when looking at the workings of the repository pinger inside AbstractSlingRepository.java:
> When a default workspace is not specified, the repository pinger will use "null" as workspace name and attempt to remove an idle session from the administrative user's session pool. It will, however, never match an existing session, since (SessionPool.java:782)
>   session.getWorkspace().getName().equals(workSpaceName)
> In other words, the repository pinger will continuously acquire "real" sessions instead of reusing a pooled one.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.