[ https://issues.apache.org/jira/browse/JCR-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783083#action_12783083 ]
Stefan Guggisberg commented on JCR-1456: ---------------------------------------- > It would mean changing the current pm implementations. So pooling wouldn't be > optional. ok, assuming that there are no known issues at this time: -0 for merging it to trunk +1 for merging it to trunk if pooling would be an optional feature > 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-performance-trunk-test-setup.patch, JCR-1456-performance.txt, > 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.