> As you wrote
> > The status goes from READ to WRITE "shortly after" the headers have been
> completely read by Apache.
> for me this sounds like Apache is trying to read req. headers during that
> time.
> I would assume this is not a problem in Apache, but probably due to client
> or network
Thank you for your help so far - maybe you could shed some light on my last
comment, please:
> But if we take that column SS out of the picture and let's say I'm
reloading server-status periodically and see that
> - a request comes in, status is Reading
> - refreshing server-status in every
Testing by telnet is a good hint, thanks!
But I'm not sure how to send half a request...
I see now what SS is for, thanks.
But if we take that column SS out of the picture and let's say I'm
reloading server-status periodically and see that
- a request comes in, status is Reading
- refreshing
On Wed, Jul 12, 2017 at 10:46 AM, Tamas Kocsis
wrote:
> If I keep and eye on server status page and see that e.g. these ? reading
> requests pending for more than a minute:
>
> Srv PID Acc M CPUSS Req Conn Child Slot Client VHost
> Request
>
Ok, so let me try to re-phrase that part:
If I keep and eye on server status page and see that e.g. these ? reading
requests pending for more than a minute:
Srv PID Acc M CPUSS Req Conn Child Slot Client VHost
Request
On Wed, Jul 12, 2017 at 10:23 AM, Tamas Kocsis
wrote:
> If we see Reading requests on Apache status page with relatively high (e.g.
> 200+) values in SS column that actually means Apache is trying to read req.
> headers for more than 3 minutes, right?
I don't think
Thank you Eric for the quick reply and the clarification!
Maybe few words about the possible reasons and background...
Our Apache is used to SSL offload and forward request to WebLogic, which is
actually facing some stuck thread issues and becoming real slow from time
to time (separate story
On Wed, Jul 12, 2017 at 9:16 AM, Tamas Kocsis wrote:
> My understanding is:
> a reading state request means that the socket was opened, but the
> request itself not yet (fully) reached Apache - thus it's waiting for the
> request to arrive 100%.
>
> Is my
Hello there!
On our Apache 2.2.23 server-status page we can see many requests in
"*R*" Reading Request
state.
Currently I'm not looking for the reasons behind, at the moment I just want
to make sure the meaning of this status is correctly interpreted by us.
Was no able to find a more