You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (Jira)" <ji...@apache.org> on 2020/01/20 05:54:00 UTC
[jira] [Commented] (JCR-4521) When will Jackrabbit support dbcp 2.0
[ https://issues.apache.org/jira/browse/JCR-4521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17019240#comment-17019240 ]
Julian Reschke commented on JCR-4521:
-------------------------------------
Classic Jackrabbit is pretty much in maintenance mode, so don't expect major improvements, unless you're willing to do them yourself.
FWIW, Jackrabbit Oak's RDB support works with any Datasource and has no direct requirement for a specific pool implementation.
> When will Jackrabbit support dbcp 2.0
> --------------------------------------
>
> Key: JCR-4521
> URL: https://issues.apache.org/jira/browse/JCR-4521
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core
> Affects Versions: 2.20
> Reporter: john tal
> Priority: Major
>
> Jackrabbit 2.20.20 (core) appears to still use commons-dbcp 1.3
> If true, based on https://issues.apache.org/jira/browse/DBCP-156 support for setting maximum connection lifetimes was added to dbcp with v 2.x (back in 2013).
> We are running Jackrabbit in an enterprise solution and all of our other content/application solutions use connection pools which support setting many connection/pool attributes such maximum connection lifetimes. But, AFAIK, not Jackrabbit.
> When tuning large applications for all aspects of the environment fine grained control over treatment of database connection pool maintenance is standard and required. But not provided in Jackrabbit (AFAIK).
> Sending the current many defaults of the datasource in Jackrabbit ConnectionFactory, is making a lot of assumptions and provides little ability for tuning based on specific environment needs.
> When will Jackrabbit upgrade from this old commons-dbcp version to something modern and provide for the ability to set custom configurations for: ?
> * Maximum connection lifetime
> * Override the current defaults in ConnectionFactory (example ds.setTestOnBorrow(false))
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)