Since the protocol relies on passive timers to determine failure and take action, there is a risk that a busy client may be slow in sending a keepalive request message to the AppServer. Careful tuning of the timer values is necessary to avoid disconnection of healthy client connections. Note that your client implementation details may add several seconds to the time it takes for the client to detect a timeout.