Re: setQueryTimeout not work?
- From: "joeNOSPAM@xxxxxxx" <joe.weinstein@xxxxxxxxx>
- Date: Fri, 30 Jan 2009 08:23:24 -0800 (PST)
On Jan 30, 2:21 am, mttc <mtczx...@xxxxxxxxx> wrote:
I check Above loop with .NET, and I got timeout exception. I not see
any reason (according the JDBC spec) to implement it only by sending
cancel to the server. the app must sure that on any situation
operation cancel after timeout.
I sure that timeout with .NET stop waiting for unplug cable, even
socket not report error. I not think that have app that prefer
behaviour of waiting eternity.
I agree with you, in that the driver could/should have a (one) utility
thread that handles all timeouts for any connections, connection
attempts, statements etc. (never have one thread per connection),
but the question is what the driver can do to make the connection
viable after the timeout. Until the DBMS does respond to the original
query or the cancel, the connection is useless...
.
- References:
- setQueryTimeout not work?
- From: mttc
- Re: setQueryTimeout not work?
- From: joeNOSPAM@xxxxxxx
- Re: setQueryTimeout not work?
- From: mttc
- setQueryTimeout not work?
- Prev by Date: Re: setQueryTimeout not work?
- Previous by thread: Re: setQueryTimeout not work?
- Index(es):
Relevant Pages
|