tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Jung <rainer.j...@kippdata.de>
Subject Re: mod_jk Status Busy Number
Date Mon, 03 Jul 2006 16:59:43 GMT
This bug has been fixed in version 1.2.16.

We just now tagged 1.2.16. A release candidate is available. Please have
a look at

http://marc.theaimsgroup.com/?l=tomcat-dev&m=115194553720728&w=2

Test results are welcome. If no new problems will be found, the release
vote will procees starting Friday.

The final release will be announced on this list and on the dev list.

Troy Davidson schrieb:
> Here is that data a bit better:
> 
> Name    Type    Host    Addr    Stat    F    V    Acc    Err    Wr   
> Rd    Busy    Max    RR    Cd
> 
> tomcat24    ajp13    10.9.100.2:24009    10.9.100.2:24009    Stopped   
> 1    6    59803    96    0     0     4294967294    48        tomcat14   
> ajp13    10.9.100.1:14009    10.9.100.1:14009    OK    1    9   
> 166945    232    0     0     19    76         
> tomcat15    ajp13    10.9.100.1:15009    10.9.100.1:15009    Stopped   
> 1    6    59812    99    0     0     4294967292    58         
> tomcat34    ajp13    10.9.100.3:34009    10.9.100.3:34009    OK    1   
> 8    166945    211    0     0     11    97         
> tomcat35    ajp13    10.9.100.3:35009    10.9.100.3:35009    Stopped   
> 1    7    59878    86    0     0     4294967293    51
> 
> Troy Davidson wrote:
>> We are doing load balancing with Apache and mod_jk.  We have five
>> instances of Tomcat running on three servers.  Two Tomcat instances
>> are fine.  But, Three Tomcat instances show really high "Busy" numbers
>> on the Status page.  Here is what it looks like:
>>
>> Name    Type    Host    Addr    Stat    F    V    Acc    Err    Wr   
>> Rd    Busy    Max    RR    Cd
>> tomcat24    ajp13    10.9.100.2:24009    10.9.100.2:24009   
>> Stopped    1    6    59803    96    0     0     4294967294   
>> 48          tomcat14    ajp13    10.9.100.1:14009   
>> 10.9.100.1:14009    OK    1    9    166945    232    0     0     19   
>> 76          tomcat15    ajp13    10.9.100.1:15009   
>> 10.9.100.1:15009    Stopped    1    6    59812    99    0     0    
>> 4294967292    58          tomcat34    ajp13    10.9.100.3:34009   
>> 10.9.100.3:34009    OK    1    8    166945    211    0     0     11   
>> 97          tomcat35    ajp13    10.9.100.3:35009   
>> 10.9.100.3:35009    Stopped    1    7    59878    86    0     0    
>> 4294967293    51    The number of Busy connections are over 4
>> billion?!?!  I didn't think we were that popular.  ;)
>>
>> The strange thing is that these numbers come and go with each refresh
>> of the page.  They will be there, hit refresh, and they are gone.  Hit
>> refresh again, and they are back.  The numbers will only bounce
>> between those three instances.  The tomcat14 and tomcat34 won't see
>> them, and work fine.
>>
>> We have had to stop those three since it was affecting the app.  It
>> seems session replication was affected.  As soon as those three were
>> stopped, things work fine.
>> The configs of the five instances are identical except for ports
>> obviously.  Has anyone seen a similar behavior?  Thanks.
>>
> 

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message