[
https://issues.apache.org/jira/browse/JCR-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768226#action_12768226
]
Martijn Hendriks commented on JCR-1456:
---------------------------------------
I think that the "testWhileIdle" approach for the DataSources managed by
Jackrabbit resolves the performance issue (this is already present in the
sandbox branch). I will try to get some more test results tomorrow. What I
intend to do is measure the time that it takes to build the jackrabbit-core up
to the integration-test phase on MySQL, MSSQL, H2 and Oracle backends. I
compare the sandbox branch with a close revision in the trunk. I hope that
these build-times are approximately the same. Is that enough, or should we do
some more measurements?
> Database connection pooling
> ---------------------------
>
> Key: JCR-1456
> URL: https://issues.apache.org/jira/browse/JCR-1456
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: Jukka Zitting
> Fix For: 2.0.0
>
> Attachments: 777490.patch, dbcp.patch, dbcp.patch, JCR-1456.patch,
> patch-1456-1.txt, patch-1456-2.txt, patch-1456-3.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.
