Re: Runaway dbaccess process
Posted in 1997
It is know bugs in Informix. This I got from my local Informix office.
Bug: 37430 WHEN PARENT PROCESS DIES THE CHILD PROCESS ACCUMULATES CPU
TIME; IT HANGS ON A READ() SYSTEM CALL WHICH RETURNS 0 BYTES (TERMINAL DIES
FOR EXAMPLE)
Date: 1995-02-23 Category: 4GL
Type: SW Submitter: pintus
Description:
The problem is that a 4GL application who is logged on to a database
terminates its connection (the terminal dies) to the database without
logging off. The user logging off without disconnecting has the read()
system call hanging. It returns 0. See /pts/bugs/37430/README
This is fixed in 4GL version 6.02. Dbaccess is coded in 4GL. for
Bug: 57230 7.20.UC2 - DBACESS SESSION CONNECT THEN CLOSE WINDOW AND
SESSION/PROCESS SIGNAL IS NOT CAUGHT AND STOPPED. CPU IS STILL GIVEN TO
SESSION
Date: 1996-08-14 Category: DBACCESS
Type: SW Submitter: donh
Description:
In 7.12.uc1 a dbaccess session terminates if the client dies or
window is closed. This also happens in an isql session. In
7.20.uc2 this functionality is not working for dbaccess although
isql 6.03.uc2 still terminates
This is fixed in OnLine 7.22.UC1
Bjarne W. Jensen /Alm. Brand