Re: Killing off client threads
Posted in 1996
Topics: Connectivity: ODBC / JDBC / .NET
The Mist (ammist@io.com) wrote: : I'm using : ODBC to connect to Informix 7.12 and occasionally, the driver does not : release the connection when my client program crashes. I'm using : Intersolv's DataDirect drivers for Informix 5 on an NT machine. I'm Interesting.... Weve experienced something like that also with a 32bit ODBC driver that we're beta testing. We found two similar bugs; The first case was where, like your situation, the application on the PC crashed or exited abnormally, but the processes on the server side stuck around in a 'zombie' state. A workaround; We wrote a script that would look at the process table, identify those that were around too(?) long, and get rid of the oldest, using lsof. We resolved it by getting new versions of the server services(HP SOLID Data Manager 5.1), and the 32bit PC driver. The second instance we found that the PC driver was developing a memory leak; It was contained to the PC; The driver is called and allocates a certain amount of memory(virtual?) for itself; When it finished, it would release most BUT NOT ALL of the allocated memory and continue in this fashion, until all available memory was used. We found that the danger really exits only for apps that continue in a loop for extended periods of time, since the process would luckily clean itself up and release memory if it finished it's work promptly, and not loop. Check out their page....some useful info. SOLID: http://solid.corp.hp.com/ Ted Martinez CIM-Engineering Hewlett Packard (VCD) Factory Information