Config: Sun E450 - 2 processors, 4GB RAM, Solaris 7,
WebSphere Application Server 3.0.2, IBM HTTP Server 1.3.6
When I do "apachectl start", and then "ps -ef |grep httpd", i get back
about 5 or 6 httpd processes. After some time, it goes up to around 35.
There are times when it goes as high as 50... Usually not a problem,
but today it went up to 159 and stayed there... web site became
extremely slow.... can't even load up the website's first page....
obviously, we got alot of phone calls :(
checked CPU utilization normal - around 5 - 10% sustained.
i checked "netstat -a" and did notice a lot of HTTP connections on
port 80. many were in ESTABLISHED state, and many more were in TIME_WAIT state.
don't know what caused this... hope somebody here can give some
i read in another article by Bill Stoddard that IBM HTTP Server
uses a process per concurrently connected client.
1) How many concurrent web connections can a server with the config
above support without extreme performance degradation??? i can't
believe a Sun E450 cannot handle 150+ concurrent web connections.
2) Where in httpd.conf can i limit the number of concurrent
connections that IBM HTTP Server will allow???
3) If 10 httpd processes are spawned off if there are 10 simultaneous
connections, if 5 of these connections disconnect, shouldn't 5 httpd
processes dissapear??? or they still stay there... what happens to
these httpd processes??? do they then cater to other web connections,
or they simply become orphaned????
Hope somebody can help. Thanks in advanced :)