activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From greg <greg.fr...@bt.com>
Subject trying to understand exactly how the server knows when a client fails
Date Wed, 17 Nov 2010 17:21:41 GMT

i would like to get a better understanding of how the server determines that
a client is alive. i have been reading about the following parameters as
much as possible:
     maxInactivityDuration, connectionTimeout, soTimeout and failover
settings.

believe it or not, what's puzzling me isn't something bad but something that
looks too good to be true.  
The test scenario is this:
  - kill a java jms client from the OS  
  - i am assuming that causes an exit without closing things cleanly.  
  - almost immediately, i see in the server log:  2010-11-17 10:11:15,494 |
INFO  | Transport failed

in such a case, i would expect the server to have to wait for some timeout
period based on the above settings before declaring the client as "dead". 
however, the server appears via logs to have nearly instantaneous awareness
that the client is gone.  i'm not complaining, this seems fantastic but i'd
like to understand better how it works before i proceed to depend on the
timing.

thanks,
greg

-- 
View this message in context: http://activemq.2283324.n4.nabble.com/trying-to-understand-exactly-how-the-server-knows-when-a-client-fails-tp3047186p3047186.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message