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 related to the hosted app.).
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 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? Some colleagues recommended to try increasing no. of Apache slots, but I think that would not make difference in terms of Reading state requests, but would make things worse for WebLogic struggling behind by allowing more requests to reach that... On Wed, Jul 12, 2017 at 3:24 PM, Eric Covener <cove...@gmail.com> wrote: > On Wed, Jul 12, 2017 at 9:16 AM, Tamas Kocsis <mr.tamas.koc...@gmail.com> > 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 understanding correct? > > The status goes from READ to WRITE "shortly after" the headers have > been completely read by Apache. This does not include the request > body. > > Some "normal" modules can still run before this transition though by > using the ap_run_pre_read_request/ap_run_post_read_request callbacks. > mod_info can tell you which loaded modules participate in this phase. > It's not common for them to be the culprit here though. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org > >
