Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 4861 invoked from network); 31 Mar 2010 23:56:14 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 31 Mar 2010 23:56:14 -0000 Received: (qmail 46306 invoked by uid 500); 31 Mar 2010 23:56:11 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 46293 invoked by uid 500); 31 Mar 2010 23:56:11 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 46285 invoked by uid 99); 31 Mar 2010 23:56:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 Mar 2010 23:56:10 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [128.122.80.9] (HELO smtp.cims.nyu.edu) (128.122.80.9) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 Mar 2010 23:56:04 +0000 Received: from KELFER.BIO.NYU.EDU (KELFER.BIO.NYU.EDU [128.122.61.181]) (authenticated bits=0) by smtp.cims.nyu.edu (8.14.3/8.13.8) with ESMTP id o2VNthYc024806 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for ; Wed, 31 Mar 2010 19:55:43 -0400 (EDT) Message-Id: From: ARTHUR GOLDBERG To: users@httpd.apache.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Wed, 31 Mar 2010 19:55:42 -0400 X-Mailer: Apple Mail (2.936) X-Virus-Checked: Checked by ClamAV on apache.org Subject: [users@httpd] Apache2::Resource Hi users@httpd As I mentioned in an earlier email, we're running mod_perl on Apache (2.2) on RHEL, using the prefork MPM. I want to protect my server against Perl processes that grow much too large, as they can slow or even freeze the system. Therefore, I'm using Apache2::Resource, adding the following to httpd.conf: > PerlModule Apache2::Resource > # set child memory limit to 1000 megabytes > # RLIMIT_AS (address space) will work to limit the size of a process > PerlSetEnv PERL_RLIMIT_AS 1000 > PerlChildInitHandler Apache2::Resource httpd processes die as expected when their VM size reaches 1000 MB. But here's the problem. After the httpd serving the Request dies, a new one is created to handle the same request. And so on. I think this is all done in Apache, as the access log doesn't show another request from the client. Is this correct? How can I limit the number of 'retries' of the failing request? Is there an Apache directive? And I'm still looking for a way to 'catch' the exception when the process dies. Regards Arthur Arthur P. Goldberg, PhD Research Scientist in Bioinformatics Plant Systems Biology Laboratory www.virtualplant.org Visiting Academic Computer Science Department Courant Institute of Mathematical Sciences www.cs.nyu.edu/artg artg@cs.nyu.edu New York University 212 995-4918 Coruzzi Lab 8th Floor Silver Building 1009 Silver Center 100 Washington Sq East New York NY 10003-6688 --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org