[
https://issues.apache.org/jira/browse/DBCP-226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719528#action_12719528
]
Pedro Faundez Gonzalez commented on DBCP-226:
---------------------------------------------
Since this is a critical bug fix for validationQuery users, will you release a
new tarbal for the stable dbcp-1.2?
I think if a validation query is specified and validationQueryTimeout is not,
either a default validationQueryTimeout should be setup or dbcp should fatal
its initialization. If you guys do not have a use case for the old behavior of
not having a timeout for the validationQuery one of there two options should be
coded.
I can not see this change at:
http://commons.apache.org/dbcp/changes-report.html
how is that page generated?
> DBCP should support configuration of queryTimeout for validation queries
> ------------------------------------------------------------------------
>
> Key: DBCP-226
> URL: https://issues.apache.org/jira/browse/DBCP-226
> Project: Commons Dbcp
> Issue Type: Improvement
> Affects Versions: 1.2.2
> Reporter: Phil Steitz
> Assignee: Phil Steitz
> Priority: Minor
> Fix For: 1.3
>
>
> Validation queries used when testOnBorrow and/or testOnReturn do not
> currently support queryTimeouts. This should be configurable.
> See http://www.mail-archive.com/commons-...@jakarta.apache.org/msg92457.html
> for background on this request made on the commons-dev mailing list.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
