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 2008/12/18 16:37:44 UTC

[jira] Resolved: (SLING-786) SessionPool logs out session on release when locking or observation is not supported

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

Felix Meschberger resolved SLING-786.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: JCR Base 2.0.4
         Assignee: Felix Meschberger

Thanks for providing this patch. I have applied it  in Rev. 727749.

Please close if this solves your issue. Thanks.

> 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.