SECONDARY_EVENT_TIMEOUT Connection Manager configuration parameter

The SECONDARY_EVENT_TIMEOUT parameter specifies the number of seconds that must elapse with no secondary-server events before the Connection Manager disconnects from a secondary server. A secondary-server event is an indication from a secondary server that the server is still functioning, such as a sent performance-statistics or administration messages.

Syntax

1  SECONDARY_EVENT_TIMEOUT
2.1 -1
2.1! 60
2.1 seconds
Table 1. Values for the SECONDARY_EVENT_TIMEOUT Connection Manager configuration parameter
SECONDARY_EVENT_TIMEOUT parameter value Description
-1 The Connection Manager waits indefinitely
0 to 30 The Connection Manager waits 30 seconds.
> 30 The Connection Manager waits the specified number of seconds.

Usage

The SECONDARY_EVENT_TIMEOUT parameter is optional, and applies CLUSTER connection units.

If the SECONDARY_EVENT_TIMEOUT parameter is not specified in the Connection Manager configuration file, the Connection Manager waits 60 seconds for secondary-server events before it disconnects from the server.

Example

In the following example, the Connection Manager disconnects from a secondary server after 300 seconds elapse with no secondary-server events.
SECONDARY_EVENT_TIMEOUT 300