Received: (qmail 25230 invoked by uid 501); 16 May 2000 17:15:01 -0000 Message-Id: <20000516171501.25229.qmail@locus.apache.org> Date: 16 May 2000 17:15:01 -0000 From: Andy Johnson Reply-To: AndyJohnson@engineer.com To: submit@bugz.apache.org Subject: JServ process periodically does not die, holding resources X-Send-Pr-Version: 3.110 >Number: 6094 >Category: mod_jserv >Synopsis: JServ process periodically does not die, holding resources >Confidential: no >Severity: serious >Priority: medium >Responsible: jserv >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Tue May 16 10:20:01 PDT 2000 >Closed-Date: >Last-Modified: Mon Jul 24 12:30:01 PDT 2000 >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: From: jon * To: Andy Johnson Cc: Subject: Re: mod_jserv/6094: JServ process periodically does not die, holding resources Date: Tue, 16 May 2000 10:34:00 -0700 on 5/16/2000 10:15 AM, Andy Johnson wrote: > 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. Huh? JServ doesn't "spawn" any child processes. The C portion starts up a single instance of the JVM if you have ApJServManual "Off", that is it. This sounds like some sort of configuration error on your part. You didn't bother posting any configuration files, log files, or other relevant setup information so I'm not going to try to guess what is going wrong for you. :-) -jon -- Java Servlet Based - Open Source | Collab.Net Bug/Issue Tracking System | now hiring smart people | From: andyjohnson@engineer.com To: jon@latchkey.com Cc: apbugs@Apache.org Subject: Re: mod_jserv/6094: JServ process periodically does not die,holding resources Date: Mon, 24 Jul 2000 15:28:19 -0400 (EDT) Cause for spawned process: One of the servlets calls the method Runtime.getRuntime() to execute a command line program. The error: An internally created shell script called 'jservctl' had the line: nohup /usr/local/jserv/bin/start >> /documents/log/nohup.log The /usr/local/jserv/bin/start script had the line: java org.apache.jserv.JServ jserv.properties &>> ${JSERV_LOGDIR}/jserv.log The fix: Removed the '&' sign from the start script line. So now it looks like: java org.apache.jserv.JServ jserv.properties >> ${JSERV_LOGDIR}/jserv.log --------------------------------------------------- Get free personalized email at http://www.iname.com >Unformatted: [In order for any reply to be added to the PR database, you need] [to include 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! ]