You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2014/12/10 13:39:12 UTC
[jira] [Updated] (OAK-2337) improve connection handling
[ https://issues.apache.org/jira/browse/OAK-2337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke updated OAK-2337:
--------------------------------
Description:
Connection pools vary in whether they implicitly rollback connections on close or not. The org.apache.commons.dbcp.BasicDataSource we use *does* rollback, which can hide coding problems. Other implementations, such as the Tomcat connection pool do not (by default).
Furthermore, when obtaining connections declare whether they are read-only upfront. This may help drivers in optimizations.
was:
Connection pools vary in whether they implicitly rollback connections on close or not. The Apache commons Datasource we use *does* rollback, which can hide coding problems. Other implementations, such as the Tomcat connection pool do not (by default).
Furthermore, when obtaining connections declare whether they are read-only upfront. This may help drivers in optimizations.
> improve connection handling
> ---------------------------
>
> Key: OAK-2337
> URL: https://issues.apache.org/jira/browse/OAK-2337
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: rdbmk
> Affects Versions: 1.1.4
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Fix For: 1.2
>
>
> Connection pools vary in whether they implicitly rollback connections on close or not. The org.apache.commons.dbcp.BasicDataSource we use *does* rollback, which can hide coding problems. Other implementations, such as the Tomcat connection pool do not (by default).
> Furthermore, when obtaining connections declare whether they are read-only upfront. This may help drivers in optimizations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)