[
https://issues.apache.org/jira/browse/DBCP-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027351#comment-13027351
]
Phil Steitz commented on DBCP-357:
----------------------------------
Looks like a good enhancement for 2.0. We should probably make it
configurable, though, whether to rely on the driver implementation or actually
fire the validation query.
> Connection validationQuery mechanism should be replaced by new method
> connection#isValid()
> ------------------------------------------------------------------------------------------
>
> Key: DBCP-357
> URL: https://issues.apache.org/jira/browse/DBCP-357
> Project: Commons Dbcp
> Issue Type: Improvement
> Affects Versions: 1.4, 1.4.1
> Reporter: Philippe Mouawad
> Labels: PERFORMANCE
> Fix For: 2.0
>
>
> 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
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
