You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by bu...@apache.org on 2006/01/30 13:47:28 UTC
DO NOT REPLY [Bug 30391] - [dbcp] Use setQueryTimeout in combination with validationQuery to recover from network problems
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=30391>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=30391
------- Additional Comments From mikko.koponen@ri.fi 2006-01-30 13:47 -------
I'm pretty sure no-one is going to do anything about these, since this bug has
been open since 2004. However, having recently been bitten by this same problem,
I'd like to comment that at least on Oracle the proposed solution wouldn't help.
This is because - in its infinite wisdom - the oracle driver calls cancel() on
the statement once the statement timeout occurs. This cancel()-method then
attempts another database roundtrip. So we are stuck on that for another eternity.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org