[JCR-4521] When will Jackrabbit support dbcp 2.0

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.20
• Component/s: jackrabbit-core
• Assignee: Unassigned
• Reporter: john tal
• Created: 18/Jan/20 16:44
• Updated: 03/Jun/20 10:47

Description

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))

 

 

Issue Links

• is related to: JCR-4579 jackrabbit-data: allow to disable statement pooling through system property