[
https://issues.apache.org/jira/browse/SLING-786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated SLING-786:
------------------------------------
Affects Version/s: JCR Base 2.0.2
> SessionPool logs out session on release when locking or observation is not
> supported
> ------------------------------------------------------------------------------------
>
> Key: SLING-786
> URL: https://issues.apache.org/jira/browse/SLING-786
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Affects Versions: JCR Base 2.0.2
> Reporter: Marcel Reutegger
> Assignee: Felix Meschberger
> Priority: Minor
> Fix For: JCR Base 2.0.4
>
> Attachments: SLING-786.patch
>
>
> There should be a check whether the repository actually supports locking
> before a query is executed to get the lock tokens. Similarly the SessionPool
> should first check if observation is supported by the repository before the
> ObservationManager is obtained. In both cases it may happen that a repository
> that does not support one or the other feature throws a RepositoryException,
> which causes the session to be closed. This effectively makes the SessionPool
> useless in that case.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
