Re: Need help: zombie user threads

In article <3gffop$1k5@cssun.mathcs.emory.edu> calvinng@technet.sg (Calvin Ng) writes: >From: calvinng@technet.sg (Calvin Ng) >Subject: Re: Need help: zombie user threads >Date: 29 Jan 1995 02:23:05 -0500 >On Fri, 27 Jan 1995, Rolf Saalfrank wrote: >> We have a problem with our client server application as described >> below: >> Windows Application >> -> Q+E ODBC driver V. 1.2 >> -> Informix NET for Windows 5.01E1 >> -> LWP Winsock interface >> -> Network >> -> Informix Online 6.00 UE1 under UNIX >> Now the problem: >> When our Windows client crashes, a user thread within Informix >> remains alive with all its database locks. A checkpoint doesnt >> help. We have to kill this thread manualy with the onmode command. >This is a fairly common problem which I have been trying to seek a >solution to for quite a long time. This phenomenon occurs in version 5.x >as well. The last time I brought this up on the net, I didn't get a >satisfactory answer. >IMHO, the server side of the connectivity has been lacking when it comes >to checking if the client is still alive. I think Informix do have to >look into this, and do something about it. (Of course, we will not raise >too much noise about why Windows' client can crash so easily) >The phenomena is suprisingly easy to reproduce. Just use a Windows's >front end to access Informix. After doing some token queries. Simulate >a crash by switching off the PC. (Anyone trying this have read my >disclaimer, and agrees to it) Please, make sure all other applications >are not running, and all data has bee saved. Next, go to the server, and >observe the SQLTURBO process (5.x), or the user thread (6.x) survive and >live happily ever after. :-) Are you looking for something that will poll for sqlturbo processes? I wrote a 2 cron shell scripts that would run at "busy" times of the day, check for the processes; verify that the transaction was not in a critial part of the DB (open tables) & kill these processes. Also, e-mail messages were sent to the user's to remind them not to leave their terminal idles, which can also cause zombie processes AND logged username & time of detachment. It requires root AND informix privileges and was written on an IBM RISC 6000 using Informix v5.?? If this "seems" like what you're looking for, then **e-mail** a response (I don't check this newsgroup regularly) and I'll look for the code, re-type it & post it (so give a few days to get it together).