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 2010/01/11 14:10:54 UTC
[jira] Updated: (SLING-1283) Remove Session Pool Support
[ https://issues.apache.org/jira/browse/SLING-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger updated SLING-1283:
-------------------------------------
Affects Version/s: (was: JCR Base 2.0.2)
JCR Base 2.0.4
Fix Version/s: JCR Base 2.1.0
> Remove Session Pool Support
> ---------------------------
>
> Key: SLING-1283
> URL: https://issues.apache.org/jira/browse/SLING-1283
> Project: Sling
> Issue Type: Task
> Components: JCR
> Affects Versions: JCR Base 2.0.4
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: JCR Base 2.1.0
>
>
> The Session Pool Support code in the jcr/base bundle has a few issues:
> * Only works with SimpleCredentials authentication
> * Wrong level of abstraction: such optimizations are the task of the repository implementation and not of the user
> * Cleanup of the session for reuse is brittle and timeconsuming (due to a JCR search to ensure unlocking transient locks)
> * Little to no gain in performance (in fact performance is even lower than using plain Jackrabbit Sessions.
> In addition, I suspect session pooling to be responsible for various strange integration test failures (see also SLING-1272).
> Therefore Session Pool support should be removed.
> See also the dev list discussion at http://markmail.org/thread/wiiqs2ym75mpfxcd
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.