[
https://issues.apache.org/jira/browse/JCR-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770041#action_12770041
]
Jukka Zitting commented on JCR-1456:
------------------------------------
The AutoCommit stuff shouldn't be needed with connection pooling anymore, the
AutoCommit mode should simply always be off.
We use the AutoCommit mode to avoid having to add explicit commit() calls even
after read-only operations. It's being switched on an off depending whether the
repository is performing a read or a write operation. Now with the connection
pool a connection is simply closed (or reclaimed to the pool) after a read
operation ends, so no pending transaction state starts to accumulate on the
database side.
> 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.
