tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 44454] busy count reported in mod_jk inflated, causes incorrect balancing
Date Mon, 14 Apr 2008 13:25:54 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=44454


Paul Martin <pcmartin@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pcmartin@gmail.com




--- Comment #15 from Paul Martin <pcmartin@gmail.com>  2008-04-14 06:25:52 PST ---
We've noticed this problem in our production environment as well...  At present
it is a low-load point in the day (when we are processing ~20 requests), yet
the busy count is reported as being 400+ (which is about MAX - 20 in
jk-status).  

Nothing short of restarts seem to correct the count.

I've literally tried all the timeout values I could find (on both ends - mod_jk
and jboss) - keeping of course in mind their intended purposes as described in
the docs - but none seemed to have any effect on the busy count not
decrementing.

I did a jboss thread dump and found 146 threads with the word "8009" in it, but
according to Rainer's analysis only a handful (11 to be exact - I grepped
RUNNABLE threads only) of them are actually processing requests.

Curiously enough, we did not seem to have this issue in our test environment
(with nearly identical configurations), even after intensive load testing.

I'm not sure if this is something specific to our environment.  For the record:

SunOS mega 5.10 Generic_127111-06 sun4v sparc SUNW,Sun-Fire-T200

Server Version: Apache/2.2.6 (Unix) mod_jk/1.2.25
JK Version:     mod_jk/1.2.25

Server version: Apache/2.2.6 (Unix)
Server built:   Jan 19 2008 22:12:59
Server's Module Magic Number: 20051115:5
Server loaded:  APR 1.2.11, APR-Util 1.2.10
Compiled using: APR 1.2.11, APR-Util 1.2.10
Architecture:   32-bit
Server MPM:     Worker
  threaded:     yes (fixed thread count)
    forked:     yes (variable process count)
Server compiled with....
 -D APACHE_MPM_DIR="server/mpm/worker"
 -D APR_HAS_SENDFILE
 -D APR_HAS_MMAP
 -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
 -D APR_USE_FCNTL_SERIALIZE
 -D APR_USE_PTHREAD_SERIALIZE
 -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
 -D APR_HAS_OTHER_CHILD
 -D AP_HAVE_RELIABLE_PIPED_LOGS
 -D DYNAMIC_MODULE_LIMIT=128
 -D HTTPD_ROOT="/usr/local/httpd-cls01"
 -D SUEXEC_BIN="/usr/local/httpd-cls01/bin/suexec"
 -D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
 -D DEFAULT_ERRORLOG="logs/error_log"
 -D AP_TYPES_CONFIG_FILE="conf/mime.types"
 -D SERVER_CONFIG_FILE="conf/httpd.conf"


We are currently running in degraded mode due to a session replication issue,
so for the time being only one node is responding to requests.  Perhaps this is
part of the equation?


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message