[DBCP-357] Connection validationQuery mechanism should be replaced by new method connection#isValid()

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4, 1.4.1
• Fix Version/s: 2.0
• Labels: PERFORMANCE
• Assignee: Unassigned
• Reporter: Philippe Mouawad
• Created: 28/Apr/11 12:08
• Updated: 31/May/14 04:12
• Resolved: 17/Feb/14 13:22

Description

Hello,
Current method of connection validation relies on validationQuery.
This method has a rather big performance impact on the DB (CPU, for example 3% with SELECT 1 FROM DUAL even with Oracle 10G FAST DUAL) and make an additional query for each borrow (when testOnBorrow is true).
Wouldn't it be better to use new JDBC 4 method isValid which relies on Driver check ? (Oracle would for example use its internal method ping)

Thank you
Philippe
http://www.ubik-ingenierie.com

Issue Links

• is duplicated by: DBCP-401 PoolableConnectionFactory.validateConnection() doesn't test connection.isValid()