Re: IDS 7.2x: open sessions without clients?

Jon Myatt wrote: > > Helmut Leininger wrote: > > > > Hi, > > > > Sometimes we are getting performance problems after about 3 to 4 days > > system up time. We have found that in that case there are a lot of > > informix session open (onstat -u) but it seems that the clients have > > died (i.e. the number of sessions is far more than the number of working > > PC's or users connected to the host system). > > > > Does anyone have an idea how to determine (preferably by a script) if > > the connection between the informix user session and the client still > > exists (the client is still alive) ? > > How about some sort of script which does onstat -u and gets the client > hostnames out and then tries to ping each one, if the ping fails, > onmode -z the session? Or get the IP addresses from netstat? No good if the PC powered down last night and you check after power up the next morning! This is a perennial problem with PC clients. PC users are used to just powering down without closing applications and killing an app from its WINDOZE menu or by double clicking the upper left corner does not properly shutdown network connections either. You can avoid this problem by disabling the TCP/IP keepalive feature. This will immediately detect client disconnection and release resources. To do this add the k=0 option to the end of appropriate line in the sqlhosts file describing the port/service name that the clients are connecting to. You do not specify your IDS version, this option and others were made available in 7.20. If you have an earlier version your system adminstrator may be able to adjust the keepalive feature default in the TCP/IP drivers using administration tools. Art S. Kagel