Session cleanup

• Mail Item Text Follows UMSG:FROM: USKIMNVM--IBMMAIL TO: INET --USIGLINK 01/19/96 11:02:55 To: INTERNET--IBMMAIL

> FROM: Tom Morris - Kimball International, Inc. (812) 482-8263
> Information Systems USKIMNVM_at_IBMMAIL.COM
>

 SUBJECT: Session cleanup

   To better explain what I meant about orphaned processes, here is some output    of a 'ps' command that shows processes left running by a user that did not    logoff, but turned off his PC with the FORMS session still running. The    -ksh login shell, iap30 forms app, menu, and oracle connection are all left    running on the Unix server.

     dkibby 26516 26513  0  Jan 17  ttysd    0:03 -ksh
     dkibby 16505 16503  0  Jan 17  ttysd    0:00 iap30 ciim dkibbyciim
     dkibby 16503 26516  0  Jan 17  ttysd    0:00
 /ciim/ciim863/ciimsys/util/menu
     oracle 16508     1  0  Jan 17  ?        1:24 oracleT028 (LOCAL=NO)

   These processes stay out there until I kill them or the server itself is    ipl'ed. Does anyone else have this problem? Is it possible/feasible to    time these out somehow?

 ...............................................................................

>UMSG:FROM: USKIMNVM--IBMMAIL TO: INET --USIGLINK 01/16/96
 14:41:28
> To: INTERNET--IBMMAIL
>
> > FROM: Tom Morris - Kimball International, Inc. (812) 482-8263
> > Information Systems USKIMNVM_at_IBMMAIL.COM
> >
> SUBJECT: 'Orphaned' user processes
>
> We've got an application using SQL*FORMS 3.0 on HP-UX 9.0.4 and the
> users access it from their PC by logging on to Unix. For various
> reasons, such as when a network problem occurs, or a power outage
> occurs, or user error, these users become disconnected from the network
> and from Oracle and HP-UX, but their sessions still exist on our HP server.
> Thus, if a user reboots his/her PC after logging on, he/she leaves
> about 4 processes hanging around. One is for the Korn shell, one for
> SQL*FORMS connection (I think), one for the script that brings up the
> menu, and one for the Oracle connection. Our weekly IPL's of the HP
> server clean these up, but sometimes we get so many that we hit the
> limit on Kernel parameters like NFILE or NPROC.
>
> My question is how do you handle cleanup of any of the 'orphaned' tasks
> I've mentioned. Since this is an Oracle list I was wondering if anybody
> had ideas on the Oracle task part, but if you have suggestions for the
> parts that are more HP-UX related that would be great too!
>
> We're on our way to moving to SQL*NET V2 from V1, and I plan to try
> out using the TIMEOUT feature which is not currently being used at any
> of your V2 production instances. We're on Oracle 7.0.16.
>
> TIA,

> Tom

?? aSession cleanup Received on Fri Jan 19 1996 - 11:12:30 CST