This is a multipart message in MIME format.
--=_alternative 001AD78165257470_=
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
What's the client API you are using and its version? If you are using ODBC
=
you can try SQL=5FATTR=5FQUERY=5FTIMEOUT attribute to set the timeout for
y=
our=20
query/statement. However I am not aware of any such issue, in case of=20
server dies client waits forever to finish the query execution (in this=20
case returning error) !! Is it possible to share your testcase and=20
possible reproduction scenario in little more details (i.e. platforms=20
used, connectivity protocl used etc)?
-Shesh
"Dirk Gunsth=F6vel" <dirk@[EMAIL PROTECTED]
>=20
Sent by: informix-list-bounces@[EMAIL PROTECTED]
05:33
To
informix-list@[EMAIL PROTECTED]
break during waiting for resultset - how to deal with?
Hi, *
I wonder if you guys have a standard way of dealing with the
following problem which is not very likely to happen but
gives you problems in batch jobs running on a regular basis:
With Informix (tested on Versions up to 9.2 - I suppose its
the same with newer versions because it is due to the
client db data exchange protocol - please correct me if I am
wrong) the following can happen:
1. client connencts
2. client sends select to server which will take lets say
a second to get the result
3. client starts waiting for server to answer
4. server dies / connection breaks
Result: client waits forever.
One way to deal with this is to kill the statement if there
is no result after some defined amout of time.
Is there a better way?
Thanks,
Dirk
--=20
--=20
-- Dirk Gunsthoevel IT Systemanalyse phone: +49 (0)251 28446-0
-- Hammer Str. 13 fax: +49 (0)251 28446-55
-- D-48153 Muenster http://www.GunCon.de/
-- "It ain't over 'til it's over."=20
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
Informix-list mailing list
Informix-list@[EMAIL PROTECTED]
001AD78165257470_=
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
<br><font size=3D2 face=3D"sans-serif">What's the client API you are using
and its version? If you are using ODBC you can try
SQL=5FATTR=5FQUERY=5FTIM=
EOUT
attribute to set the timeout for your query/statement. However I am not
aware of any such issue, in case of server dies client waits forever to
finish the query execution (in this case returning error) !! Is it
possible
to share your testcase and possible reproduction scenario in little more
details (i.e. platforms used, connectivity protocl used etc)?</font>
<br>
<br><font size=3D2 face=3D"sans-serif">-Shesh<br>
</font>
<br>
<br>
<br>
<table width=3D100%>
<tr valign=3Dtop>
<td width=3D40%><font size=3D1 face=3D"sans-serif"><b>"Dirk
Gunsth=F6v=
el"
<dirk@[EMAIL PROTECTED]
> </font>
<br><font size=3D1 face=3D"sans-serif">Sent by:
informix-list-bounces@[EMAIL PROTECTED]
>
<p><font size=3D1 face=3D"sans-serif">22/06/2008 05:33</font>
<td width=3D59%>
<table width=3D100%>
<tr valign=3Dtop>
<td>
<div align=3Dright><font size=3D1 face=3D"sans-serif">To</font></div>
<td><font size=3D1 face=3D"sans-serif">informix-list@[EMAIL PROTECTED]
>
<tr valign=3Dtop>
<td>
<div align=3Dright><font size=3D1 face=3D"sans-serif">cc</font></div>
<td>
<tr valign=3Dtop>
<td>
<div align=3Dright><font size=3D1 face=3D"sans-serif">Subject</font></div>
<td><font size=3D1 face=3D"sans-serif">Connection break during waiting for
resultset - how to deal with?</font></table>
<br>
<table>
<tr valign=3Dtop>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=3D2>Hi, *<br>
<br>
I wonder if you guys have a standard way of dealing with the<br>
following problem which is not very likely to happen but<br>
gives you problems in batch jobs running on a regular basis:<br>
<br>
With Informix (tested on Versions up to 9.2 - I suppose its<br>
the same with newer versions because it is due to the<br>
client db data exchange protocol - please correct me if I am<br>
wrong) the following can happen:<br>
<br>
1. client connencts<br>
2. client sends select to server which will take lets say<br>
a second to get the result<br>
3. client starts waiting for server to answer<br>
4. server dies / connection breaks<br>
<br>
Result: client waits forever.<br>
<br>
One way to deal with this is to kill the statement if there<br>
is no result after some defined amout of time.<br>
<br>
Is there a better way?<br>
<br>
Thanks,<br>
Dirk<br>
<br>
-- <br>
-- <br>
-- Dirk Gunsthoevel IT Systemanalyse phone: +49 (0)251 28446-0<br>
-- Hammer Str. 13
fax: +49 (0)251 28446-55<br>
-- D-48153 Muenster
http://www.GunCon.de/<br>
-- "It ain't over 'til it's
over." <br>
<br>
<br>
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<br>
Informix-list mailing list<br>
Informix-list@[EMAIL PROTECTED]
>
http://www.iiug.org/mailman/listinfo/informix-list<br>
</font></tt>
<br>
--=_alternative 001AD78165257470_=--
|
