[
https://issues.apache.org/jira/browse/SLING-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601093#action_12601093
]
Felix Meschberger commented on SLING-488:
-----------------------------------------
What is even worth, the pool is filled with sessions while new sessions keep
getting acquired.
I am fixing this by resetting the default workspace setting of the
AbstractSlingRepository to the name of the workspace of a session returned upon
being called with a null-workspace.
> 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
> Fix For: 2.0.0
>
>
> 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.
