[
https://issues.apache.org/jira/browse/JCR-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616064#action_12616064
]
Matej Knopp commented on JCR-1456:
----------------------------------
Hi,
Thanks a lot for the comment. You're right, there might be a problem with
different connections obtained. This could be handled by attaching active
connection to current thread, so that the nested calls would always obtain the
active connection. Anyway, I will look into it and post a new patch.
I agree that this is a substantial change and will require lot of testing. But
i think at some point it will be necessary to bite the bullet and implement
connection pooling, whether it will be based on my patch or not. The current
situation is rather problematic, keeping opened connection per workspace
doesn't scale well at all.
> 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
>
>
> 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.
