Skip to Content.
Sympa Menu

freetds - RE: [freetds] dbsqlexec blocks indefinitely.

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: 'FreeTDS Development Group' <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] dbsqlexec blocks indefinitely.
  • Date: Tue, 4 Nov 2003 17:17:16 -0500

> From: Kaveri, Ramesh [mailto:ramesh.kaveri AT intel.com]
> Sent: November 4, 2003 3:19 PM
>
> In the API status appears that function dbsettime() present but
> non-functional and dbdataready is also not available yet

Correct. :-(

> The problem is that when you call dbsqlexec()/dbsqlok() on a database
> that
> has just gone offline (i.e after calling dbopen() successfully), it
> blocks
> indefinitely (even if I return INT_EXIT or INT_CANCEL from the error
> handler). On one of the reply they said it is fixed in 0.61 but we
> still see the problem.

I think db-lib would respond correctly to your handler, but it's not clear
that libtds is sending a timeout message.

> How can I prevent it from becoming blocked?

Well, it would be nice if the above worked....

dbpoll() is Sybase's equivalent to dbdataready(). It's not implemented, but
appears to be a thin wrapper around poll(2), which shouldn't be too hard to
set up. If you're not up to writing dbpoll() send us a unit test and I'll
see what I can do.

Regards,

--jkl
-----------------------------------------
The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above. If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the original
message. Please note that we do not accept account orders and/or instructions
by e-mail, and therefore will not be responsible for carrying out such orders
and/or instructions.






Archive powered by MHonArc 2.6.24.

Top of Page