[
https://issues.apache.org/jira/browse/JCR-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623419#action_12623419
]
Thomas Mueller commented on JCR-1456:
-------------------------------------
What about doing that for DbDataStore first? The patch would be much smaller.
> attaching active connection to current thread, so that the nested calls would
> always obtain the active connection
That sounds too complicated, too tricky, and too slow for me. For
store(ChangeLog), why not simply pass the connection object to the nested calls?
> require lot of testing
Just to make sure: You mean automated tests, right? Manual tests is a
maintenance problem.
> Database connection pooling
> ---------------------------
>
> Key: JCR-1456
> URL: https://issues.apache.org/jira/browse/JCR-1456
> Project: Jackrabbit
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: Jukka Zitting
> Fix For: 1.5
>
> Attachments: patch-1456-1.txt, patch-1456-2.txt
>
>
> Jackrabbit should use database connection pools instead of a single
> connection per persistence manager, cluster journal, or database data store.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
