[
https://issues.apache.org/jira/browse/JCR-4521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18054453#comment-18054453
]
Julian Reschke commented on JCR-4521:
-------------------------------------
Resolved by applying Ole Osterhagen's PR
https://github.com/apache/jackrabbit/pull/320 - thanks.
> upgrade to commons-dbcp2
> ------------------------
>
> 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
> Fix For: 2.24, 2.23.4
>
> Attachments: JCR-4521.diff
>
>
> 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.20.10#820010)
