httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Goodinson" <Dan.Goodin...@businessobjects.com>
Subject [users@httpd] n00b question - too many Apache child processes?
Date Thu, 24 Jun 2004 12:48:20 GMT
Hi,

This is the first time I've used this list - please be gentle with me!
If I should do anything wrong, please let me know and I'll make a mental
note for next time ;-)

My problem is this...  I have Apache 1.3.27 (not IHS) running on an AIX
5l system.  I am a support engineer for a BI company, and recently our
web application has been causing some issues.  I've received some
information about the problem system, and the output from "ps -ef" is
troubling me...

I am seeing what I think to be too many Apache child processes.  It may
turn out to be normal, but I wanted to check as I'm not sure.  e.g. I'm
seeing 50+ child processes all spawned by the same user who runs the BI
app.  I guess that this means that our BI app is ultimately causing
these processes to be spawned and I wonder if there is a reason for so
many children, or whether I may limit the number of children.  (Our app
uses Apache and Tomcat)

To my knowledge, the Apache installation is 100% default: I am not aware
of _any_ changes to httpd.conf.  The associated app server is Tomcat
4.1.27.

Output from "ps -ef" shows me all my expected processes, but also large
sections like this:

 

 webiadm  69206 134334   0 09:10:46      -  0:00
/opt/local/apache/bin/httpd    
 webiadm  71234 134334   0 09:18:02      -  0:00
/opt/local/apache/bin/httpd    
 webiadm  71712 134334   0 07:15:54      -  0:00
/opt/local/apache/bin/httpd    
 webiadm  75824 134334   0 09:15:25      -  0:00
/opt/local/apache/bin/httpd    
 webiadm  80450 134334   0 07:49:36      -  0:00
/opt/local/apache/bin/httpd    
 webiadm  88650 134334   0 09:15:24      -  0:00
/opt/local/apache/bin/httpd    
 webiadm  92076 134334   0 09:15:25      -  0:00
/opt/local/apache/bin/httpd    
 webiadm  92464 134334   0 09:26:14      -  0:00
/opt/local/apache/bin/httpd    
 webiadm  93556 134334   0 07:11:26      -  0:00
/opt/local/apache/bin/httpd    
 webiadm  97104 134334   0 09:11:31      -  0:00
/opt/local/apache/bin/httpd    
 webiadm  98402 134334   0 09:08:41      -  0:00
/opt/local/apache/bin/httpd    
 webiadm 100034 134334   0 07:14:49      -  0:00
/opt/local/apache/bin/httpd    
 webiadm 100638 134334   0 09:33:09      -  0:00
/opt/local/apache/bin/httpd    
 webiadm 105378 134334   0 09:19:37      -  0:00
/opt/local/apache/bin/httpd    
 webiadm 109958 134334   0 09:11:30      -  0:00
/opt/local/apache/bin/httpd    
 webiadm 114060 134334   0 09:06:56      -  0:00
/opt/local/apache/bin/httpd    
 webiadm 114506 134334   0 07:11:26      -  0:00
/opt/local/apache/bin/httpd    
 webiadm 115422 134334   0 07:11:26      -  0:00
/opt/local/apache/bin/httpd    
 webiadm 119274 134334   0 09:26:13      -  0:00
/opt/local/apache/bin/httpd    
 webiadm 119726 134334   0 09:12:11      -  0:00
/opt/local/apache/bin/httpd    
 webiadm 120964 134334   0 07:31:20      -  0:00
/opt/local/apache/bin/httpd    
 webiadm 121692 134334   0 09:34:12      -  0:00
/opt/local/apache/bin/httpd    
 webiadm 122036 134334   0 09:16:41      -  0:00
/opt/local/apache/bin/httpd    
 webiadm 125096 134334   0 08:02:06      -  0:00
/opt/local/apache/bin/httpd    
 webiadm 126780 134334   0 07:14:47      -  0:00
/opt/local/apache/bin/httpd    
 webiadm 127810 134334   0 09:16:28      -  0:00
/opt/local/apache/bin/httpd    
 webiadm 128352 134334   0 07:11:26      -  0:00
/opt/local/apache/bin/httpd    
 webiadm 130188 134334   0 09:15:08      -  0:00
/opt/local/apache/bin/httpd    
 webiadm 131674 134334   0 09:23:33      -  0:00
/opt/local/apache/bin/httpd    
 webiadm 132574 134334   0 07:14:13      -  0:00
/opt/local/apache/bin/httpd    
 webiadm 133882 134334   0 07:11:26      -  0:00
/opt/local/apache/bin/httpd 

The server hosts a 24-hour application, so perhaps it is normal for so
many child processes (since Apache rarely gets restarted) but something
doesn't seem right.  I've searched at apache.org for info in the FAQ
section, but so far I've found nothing that explains this.

Is this, in fact, normal??  If not, is there a reason for this
behaviour, or is there a directive I can set to limit the max number of
child processes?  (e.g. threadsperchild, maxthreads - can these have any
negative effect on performance?)  Do these child processes have a
limited lifetime, and would it be possible to reduce their lifespan?

Thanks in advance,
Dan.


	

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> 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


Mime
View raw message