Re: Fw: timeout using SDK 2.81 TC3 - .NET Managed Provider
--0__=08BBE582DFB3F38F8f9e8a93df938690918c08BBE582DFB3F38F Content-type: multipart/alternative; Boundary="1__=08BBE582DFB3F38F8f9e8a93df938690918c08BBE582DFB3F38F" --1__=08BBE582DFB3F38F8f9e8a93df938690918c08BBE582DFB3F38F Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: quoted-printable Hi Eric, Thanks Very Much Eric, Actually this is an expected behavior than a problem. Based on the CommandTimeout value the .NET provider informs the underly= ing ODBC driver to time out the executing query. ODBC driver then send an interrupt query to database server. I guess the problem may be on CSDK 2.70 ODBC driver; it fails to interr= upt the query. Can you please give me some more detail regarding the query that the application is executing. How long this query takes to execute. Also how many second after since it starts the execution the applicatio= n throwing error etc. Really appreciate your help. Regards, Satyan Software Engineer R&D - IBM Data Management Group 11200 Lakeview, Lenexa, KS 66219 Tel: 913 599 8792 (T/L: 337-8792) = -=3DEric=3D- = <eric@fakeisp.net = > = To Sathyanesh = 09/15/2004 08:30 Krishnan/Lenexa/IBM@IBMUS = PM = cc = Subj= ect Please respond to Re: Fw: timeout using SDK 2.81 T= C3 eric - .NET Managed Provider = = = = = = = Satyan: We have been able to avoid the timeout issue by changing our code. But no such code was required in SDK 2.7 - commands did not time out be default. This change in the default behavior is now causing us to have to change, test, and redeploy all of our code. Also - I can say for sure that this timeout is not related to .NET - otherwise, we would have seen timeouts using SDK 2.7 (assuming we do not explicitly set the timeout). But this is not what we are seeing in our tests. Additionally, we were able today to replicate the timeout using the managed provider, so this affects not only ODBC but the managed wrapper as well... I sincerely appreciate the response...if this information prompts you or your team to think of any additional information, I'm sure many people can benefit from your insight. -=3DEric=3D- --- Sathyanesh Krishnan <satyan@us.ibm.com> wrote: > > > > > > Hi Eric, > > Most probably this may be due to the CommandTimeoutt > value, by default it > is 30 sec. > (Microsoft.Data.Odbc.OdbcCommand.CommandTimeout ) > A value of 0 indicates no timeout limit, and will > wait indefinitely. > > By default the .Net application expects a query to > be finish with in 30 > second. > In case if an application issue a query that take > more than 30 > then the application should explicitly set an > appropriate time out value. > > Dim myCommand As New OdbcCommand > myCommand.CommandTimeout =3D 0 > > > Regards, > Satyan > > Software Engineer > R&D - IBM Data Management Group > 11200 Lakeview, Lenexa, KS 66219 > Tel: 913 599 8792 (T/L: 337-8792) > > > > > > Abhishek > > Mathur/Lenexa/IBM > > > To > 09/15/2004 12:35 Sathyanesh > > PM > Krishnan/Lenexa/IBM@IBMUS > > cc > > > > Subject > Fw: timeout > using SDK 2.81 TC3 - > .NET Managed > Provider > > > > > > > > > > > > > > > > Hey Satyan, > Did you have a chance to look at this in the > IIUG? > > Cheers, > Abhi > -------------------------------------------------------------------- > There are 10 kinds of people,,,,, > .... those who understand binary notations, and > those who don't. > -------------------------------------------------------------------- > > ----- Forwarded by Abhishek Mathur/Lenexa/IBM on > 09/15/2004 12:34 PM ----- > > > eric@fakeisp.net > > (-=3DEric=3D-) > > Sent by: > To > owner-informix-li > informix-list@iiug.org > st@iiug.org > cc > > informix-list@iiug.org, > > owner-informix-list@iiug.org > 09/13/2004 09:55 > Subject > PM timeout using > SDK 2.81 TC3 - .NET > Managed > Provider > > > Please respond to > > eric@fakeisp.net > > (-=3DEric=3D-) > > > > > > > > > > We have a showstopper issue...after upgrading from > SDK 2.7x to 2.81 > TC3 (to get the .NET managed provider), we're > occasionally running > into timeout errors in .NET applications. > Specifically, the.NET code > is throwing this: > > Error Message : > ERROR [HYT00] [Informix][Informix ODBC > Driver]Timeout expired. > ERROR [HY008] [Informix][Informix ODBC > Driver][Informix]Statement > interrupted by user. > Stack Trace=3D at > Microsoft.Data.Odbc.OdbcConnection.HandleError(IntPtr > hHandle, SQL_HANDLE hType, RETCODE retcode) > at > Microsoft.Data.Odbc.OdbcCommand.ExecuteReaderObject(CommandBehavior > behavior, String method) > at Microsoft.Data.Odbc.OdbcCommand.ExecuteNonQuery() > at OurCompany.WWWServices.Methodname(XmlNode > inputDoc) > Source=3Diclit09b.dll > > I've been unable to figure out, either in the > documentation or on the > 'net how to change the default timeout. I think it > might be possible > within the code, but this is a major problem - we're > not about to go > revamp our entire codebase. > > If anyone has seen this or has suggestions, we're > all ears. So far, > we've tried inserting various things into the > connection string, > setting the CONTI