Comm. Bridge General Configuration › Executing the Comm. Bridge › Client Monitor

Client Monitor

The Client Monitor Enable and Idle Time fields control how long a client remains connected to the Comm. Bridge after a completed cooperative flow. A flow is considered complete when the target server has returned its response back to the client. If the target server has not yet responded, possibly due to a long running process, its associated client will not be subjected to the idle time check. Only completed flows are subject to idle time checks.

Any client connections that have been idle longer than the Idle Time period are subject to automatic disconnection. To reduce timeout thread processing overhead, the Comm. Bridge is not using individual timer events per connection to drive the timeout expiration process. Periodically, (partially derived from the configured timeout value) the Comm. Bridge runs through its list of client connections looking for those that meet the timeout criteria. There is a trade off between timely disconnect of idle clients and constant processing of the client connection list. Small values of timeout should not be allowed to consume a large percentage of CPU processing time, nor should there be an extremely long disconnect lag time when a large timeout value is specified.

Depending upon the current idle time of a particular client, when the client list is processed, client disconnect can happen at two extreme time intervals or at any time between those intervals. These time values are somewhat dependent upon the configured timeout interval.

The minimum and maximum disconnect times are: