Re: Apache::SizeLimit Exit is Delayed
Hi Jay, Perrin, and Geoff, Thanks for your thoughts on this problem. Jay yohimbe Thorne wrote: For what its worth, I'd recommend KeepAlive Off for almost any mod_perl deployment. It basically is a waste of memory and a process slot. Especially if you put graphics on a separate server. My setup uses a mod_backhand hack for single host accelerating, And I'm using KeepAlive On based on this advice from Theo Schlossnagle. It's been working great for many months. Theo Schlossnagle wrote (on 2/22/2001): Also, be sure to turn on KeepAlives on the mod_perl server! You will no longer run out of children and mod_backhand will keep pools of open connections so that you don't have to reconnect for every request. Perrin Harkins wrote: Try changing the call $r-child_terminate() to Apache::exit(). If this seems to work better for you, let me know and I'll consider changing this in a future release of Apache::SizeLimit. Geoff wrote: what about $r-headers_out-add(Connection = 'close'); I tried each of these changes in turn. Neither worked to immediately exit the child. I never saw that either of them would exit the child at all but I may not have kept them running long enough. I noticed an odd pattern of behavior. With one of our cgi scripts, and using $r-child_terminate(), the child would always exit immediately. With other scripts, it wouldn't exit. With both Perrin's and Geoff's suggestions from above, that same script would cause the process being used to be changed, but the old process wouldn't exit. We're going to try to figure out what is happening with this and I'll report back if we do. Thanks again for your help! Bob
Apache::SizeLimit Exit is Delayed
Hi, I'm using Apache::SizeLimit (on both Solaris and Linux) and getting the error_log entry: [Tue Dec 11 15:01:19 2001] (2520) Apache::SizeLimit httpd process too big, exiting at SIZE=44964 KB SHARE=10900 KB REQUESTS=389 LIFETIME=9505 seconds But the child process often doesn't exit right away. It may hang around for a couple of minutes or even an hour with the message occuring with every hit: [Tue Dec 11 15:20:22 2001] (2520) Apache::SizeLimit httpd process too big, exiting at SIZE=48852 KB SHARE=10944 KB REQUESTS=458 LIFETIME=10648 seconds Eventually the child will exit. (I'd like it to exit on the very first occurrence.) I've looked through the documentation and the archives and can't find a solution to this. Can anyone give me some insight? Thanks! Bob Foster
Re(2): Apache::SizeLimit Exit is Delayed
[EMAIL PROTECTED] writes: I'm using Apache::SizeLimit (on both Solaris and Linux) and getting the error_log entry: [Tue Dec 11 15:01:19 2001] (2520) Apache::SizeLimit httpd process too big, exiting at SIZE=44964 KB SHARE=10900 KB REQUESTS=389 LIFETIME=9505 seconds But the child process often doesn't exit right away. It may hang around for a couple of minutes or even an hour with the message occuring with every hit: Maybe this is because of a keep-alive connection. It's possible that Apache::exit() waits for all keep-alive activity to complete before exiting. Is there any way you can test it without keep-alive? - Perrin Hi Perrin, That was it. The child exited immediately when I hit the limit with KeepAlive Off. Now the question is: Is there a way to force an exit even with KeepAlive On? Thanks! Bob