Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

When I look the mod_status page I see the following (using mod_proxy to send request to tomcat):

9.56 requests/sec - 46.4 kB/second - 4970 B/request 193 requests currently being processed, 57 idle workers

Does requests currently being processed mean currently 193 requests are waiting a response from tomcat ? If it is so, there is a problem here right ? We should expect to see a similar number for requests/sec and requests currently being processed ? So this means tomcat is responding late (comparing to requests per second) ?


share|improve this question

migrated from Oct 3 '11 at 14:15

This question came from our site for professional and enthusiast programmers.

up vote 0 down vote accepted

Not necessarily.

If you're returning large responses, it might be that it's taking a while to send.

If you enable Extended Status, you'll get a report that has the details of each connection. In the 'M' column you should see one of:

"_" Waiting for Connection, "S" Starting up, "R" Reading Request,
"W" Sending Reply, "K" Keepalive (read), "D" DNS Lookup,
"C" Closing connection, "L" Logging, "G" Gracefully finishing,
"I" Idle cleanup of worker, "." Open slot with no current process

If most of the stuff is R, then it might be Tomcat ... if it's mostly W, it's just taking a while to send to the users (who may have slow connections for whatever reason ... I once had someone point their iPhone app images on our server, and I had this behaviour for a few days 'til we got them to cache the images and serve 'em themselves.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.