Hanging Sqlturbo's
Posted in 1995
Topics: Connectivity: ESQL/C, 4GL & Embedded SQL
Is there anyone that can shed any light on the following problem. A brief explanation of what the problem is is as follows : The site has the problem that at seemingly random periods during the month, the spawned "sqlturbo" processes become "parentless" and then take as long as two hours to be released by the Online engine. The setup on the site is as follows : Platform - IBM RISC 6000 (360) OS - AIX 3.2.5 Database - Informix Online 5.0 - Informix 4GL 4.1 (RDS) Users - 64 Other Software - Fourgen Accounting, CaseTools, etc Other Info - A lot of the original software is hand written, although all of the new stuff is written via the case tool. In more detail, what occurs is that as each user process is started up, the database connection is spawned (sqlturbo). The user works within the relevant screen / report and then exits back to the menu. At this stage, both the sqlturbo and fglgo process should die. However, the sqlturbo continues to "live" for up to 2 hours and is an unattached process. The result of all of this is that the USER limit (as in the tbconfig) of 120 is soon exceeded and users then have to wait until all of the "hanging" sqlturbo's die off by themselves. At any one stage, we can have as many as 118 sqlturbos existing of which 60 - 70 are "hanging". Various Online engine configurations have been tried but with no success. Any suggestions or possible solutions ??? Michael Engelbrecht