mod_jserv/6094: JServ process periodically does not die, holding resources

[Andy Johnson <An...@engineer.com>]

>Number:         6094
>Category:       mod_jserv
>Synopsis:       JServ process periodically does not die, holding resources
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    jserv
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Tue May 16 10:20:01 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator:     AndyJohnson@engineer.com
>Release:        1.3.12
>Organization:
apache
>Environment:
AIX 4.2.1.0  JDK 1.1.8ga  JITC is off (Working on applying JDK1.1.8 patches but it is
a production system and there is normal BS...)  JServ 1.1
>Description:
JServ runs as a daemon process spawning children as needed to handle requests.   
Some of those spawned processes do not die.  I have had to create a cron entry
which kills JServ procs which are older than 4 minutes.  The Servlet tasks complete
with an average time of 2 seconds, longest is 30 seconds.
>How-To-Repeat:
Not sure...  Is there some debugging flags I can turn on to get 
you appropriate information?  This was occurring with apache 1.3.6 / Jserv 1.0 also.

>Fix:
I have not been able to reproduce the error in a test environment.  The test
environment mirrors production except for the amount of RAM and the volume of requests.
Any suggestions for debugging??
>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <ap...@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]