"Orphaned" sql session
Posted in 1998
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? 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 ) Regards, Terence