Re: "Orphaned" sql session

In article <34FFC546.5F0828F0@dbs.com.sg>, Terence Chang <tat_mun@dbs.com.sg> writes >Hi, > I wondered if anyone can shed some light on this: > > I have a client program running on win 95 issuing a series of >INSERT statements dynamically. This program experiences a Illegal >Operation error (or GPF in the good old Win 3.x days) and exit >abnormally. Will the sql session at the server be killed or will it >remain an orphaned.session? If there's such a thing as orphaned >session, are there any means to prevent it from happening? > No, it is waiting for the PC to send the next SQL statement to it.. > I found such an " INSERT " sql session actually lock up one of my >tables and seems to be in a cond wait (netnorm) state. Is there any >means to kill the session implicitly via the setting of some time-out >variables either at the client (I-connect) or server. > > My system configuration: 7.23 UC4 ODS with 7.23 I-connect (win 95 >) > The UNIX TPC/IP keepalive parameters needs to be set... >Regards, >Terence > > > > -- David Williams Maintainer of the Informix FAQ Primary site (Beta Version) http://www.smooth1.demon.co.uk Official site http://www.iiug.org/techinfo/faq/faq_top.html I see you standin', Standin' on your own, It's such a lonely place for you, For you to be If you need a shoulder, Or if you need a friend, I'll be here standing, Until the bitter end... So don't chastise me Or think I, I mean you harm... All I ever wanted Was for you To know that I care