Digvijoy Chatterjee wrote:
So there are two scripts I am using as a test firefox 3.0.8 , launch
test.cgi and you can see it provides a link to another cgi script
which sleeps for 60 seconds.
I launch this link again and again in a new tab/window , but any given
time only one process has been star
So there are two scripts I am using as a test firefox 3.0.8 , launch
test.cgi and you can see it provides a link to another cgi script
which sleeps for 60 seconds.
I launch this link again and again in a new tab/window , but any given
time only one process has been started by apache on the host.
H
Digvijoy Chatterjee wrote:
I already tried that and it does not help .
Ok then.
What you report is of course not the way it should work.
If Apache was always working that way, then half the hundreds of
thousands of Apache servers on this planet woould be on their knees,
including mine.
And
I already tried that and it does not help .
On Sat, Aug 1, 2009 at 4:34 PM, André Warnier wrote:
> Digvijoy Chatterjee wrote:
>>
>> Ok so mod_status helped me make an interesting observation :
>>
>> There is only one child picking up the request for sleep.cgi when i
>> launch it new in new tabs/
Digvijoy Chatterjee wrote:
Ok so mod_status helped me make an interesting observation :
There is only one child picking up the request for sleep.cgi when i
launch it new in new tabs/ new windows, rest are children all waiting,
and picking the next requests when this one gets done .
I will repe
Ok so mod_status helped me make an interesting observation :
There is only one child picking up the request for sleep.cgi when i
launch it new in new tabs/ new windows, rest are children all waiting,
and picking the next requests when this one gets done .
Srv PID Acc M CPU S
Digvijoy Chatterjee wrote:
Apache does not process them concurrently but serially all of them go
to completion .( no error code etc..)
One request runs , other requests wait to get processed, and so on.
Have you tried
KeepAlive off
?
---
Apache does not process them concurrently but serially all of them go
to completion .( no error code etc..)
One request runs , other requests wait to get processed, and so on.
while i try mod_status to check ExtendedStatus
I have been able to simplify our problem as below.
Just put test.cgi and
Hi Digz
Meanwhile, when you say that "apache will not service any other CGI
requests", what exactly do you mean? Did you mean that your further HTTP
requests returned with 503 or some other error code? Or do they just wait
around for a long time before returning any data?
You should enable mod_st
Hi,
We are running apache 2.0.35 on RHEL4 running in prefork mode.
Its a standard apache configuration for running cgi scripts. I can
send it if required
The behaviour we are observing with apache is after servicing 2 cgi
requests which (do a long database lookup ~5 minutes)
apache will not servi
10 matches
Mail list logo
