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 secs and see the very same request in the very same Reading state > - I can see this pending Reading status of the same request for 2-3 minutes > Then what does this mean? On Thu, Jul 13, 2017 at 9:26 AM, Tamas Kocsis <mr.tamas.koc...@gmail.com> wrote: > 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 server-status in every secs and see the very same request in > the same Reading state > - I can see this pending Reading status for 2-3 minutes > Then what does this mean? > > 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 issues "only" and also has nothing to do with the slowly dying > Weblogic behind. > What do you think? > > On Wed, Jul 12, 2017 at 7:21 PM, Eric Covener <cove...@gmail.com> wrote: > >> On Wed, Jul 12, 2017 at 10:46 AM, Tamas Kocsis >> <mr.tamas.koc...@gmail.com> 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 CPU SS Req Conn Child Slot Client >> VHost >> > Request >> > ------------------------------------------------------------ >> ----------------------------------------------------- >> > 0-0 7078016 0/0/3669 R 0.03 29 493 0.0 0.00 42.55 ? ? >> > ..reading.. >> > 1-0 3408764 0/49/3988 R 0.05 50 3 0.0 0.16 96.62 ? ? >> > ..reading.. >> > >> > Does that actually mean Apache is trying to read req. headers for more >> than >> > a minute? >> I don't think so, I think it means 1 minute ago a response completed >> on that slot. You can quickly test by telnet'ing to httpd and issuing >> half a request and reloading server-status periodically. The SS will >> be larger than expected because ti's not from the beginning of the >> current request being read. >> >> -- >> Eric Covener >> cove...@gmail.com >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org >> For additional commands, e-mail: users-h...@httpd.apache.org >> >> >
