commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 30391] - [dbcp] Use setQueryTimeout in combination with validationQuery to recover from network problems
Date Wed, 05 Sep 2007 14:54:09 GMT
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 john.lonergan@ubs.com  2007-09-05 07:54 -------
Re "So we are stuck on that for another eternity"

This is not necessarily so.

One situation in which a client can hang is if the database machine dies 
suddenly while the client is in the middle of a read() operation on the socket 
during the validation query processing.
In this case the validation call would hang until the TCP keepalive (often 2 
hours by default) causes the client side read() to fail.

A statment query timeout would avoid this - since the additional 
subsequent 'database roundtrip' mentioned would fail immediately because this 
new TCP activity (ie write()) would cause an immediate network error to be 
detected.


-- 
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: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message