[
https://issues.apache.org/jira/browse/DBCP-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588536#action_12588536
]
Gerhard Kersten commented on DBCP-263:
--------------------------------------
For us it's the same, and it's really mission-critical.
Background: A firewall cuts a TCP connection after some time, but does not
close it. With "validationQuery" dbcp waits forever for the validation query,
making this feature completely useless.
For a proposal see: http://www.mail-archive.com/[EMAIL PROTECTED]/msg92474.html
> Use a queryTimeout for the validationQuery in PoolableConnectionFactory
> -----------------------------------------------------------------------
>
> Key: DBCP-263
> URL: https://issues.apache.org/jira/browse/DBCP-263
> Project: Commons Dbcp
> Issue Type: Improvement
> Affects Versions: 1.2, 1.2.1, 1.2.2
> Reporter: Christoph Grothaus
> Priority: Minor
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> PoolableConnectionFactory.validateConnection(Connection conn) should use
> java.sql.Statement.setQueryTimeout(int) to avoid network problems and
> inappropriate validation queries. The timeout should either be a sensible
> default (say 5 secs) or be configurable.
> Links:
> -
> http://svn.apache.org/viewvc/commons/proper/dbcp/trunk/src/java/org/apache/commons/dbcp/PoolableConnectionFactory.java?view=markup
> -
> http://java.sun.com/j2se/1.5.0/docs/api/java/sql/Statement.html#setQueryTimeout(int)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
