Re: Runaway dbaccess process

On 7 Oct 1997, Ron M. Flannery wrote: > On our current application, users start dbaccess and sometimes disconnect > without properly exiting (turning off terminal, etc.). The dbaccess > process hangs and proceeds to take over ALL of CPU 1 or 2. When I do a top > or sar, one of the CPUs is pegged by the dbaccess process! I was able to > easily reproduce this by starting dbaccess, doing "select * from customer" > and disconnecting. This is probably unrelated to dbaccess. When you disconnect while running certain interactive applications, they can go into a spin cycle like you've described. pine is one of the more notorious offenders. I'm not enough of a systems nerd to explain why, but I doubt its entirely an Informix problem. -Richard