Use the COORD_TIMEOUT parameter in the [CONFIG] section of the OpenSwitch server configuration file to specify the number of seconds OpenSwitch waits for a response before determining that a CM is not responding. The default COORD_TIMEOUT value is zero (0) seconds.
If you set COORD_TIMEOUT value
to zero in the OpenSwitch configuration file, concurrent CMs are
not used.
In a legacy, pre-15.0 CM application, you must set COORD_TIMEOUT to zero (0) in the [CONFIG] section of the OpenSwitch configuration file, or the CM receives an error message and does not start.
If a CM does not respond within the COORD_TIMEOUT period, the OpenSwitch server acquires the next CM ID from the internal list of inactive CMs. The previous CM ID becomes obsolete. If the CM becomes active again, it requests a new CM ID from the OpenSwitch. This occurs in the CM API and is transparent to applications.
If a connection is lost because OpenSwitch fails for some reason, the callback handler for COORD_CB_LOST is called for any CM that has lost the connection. When OpenSwitch restarts, if the CMs that lost their connection detect that the OpenSwitch has restarted, those CMs reconnect and are issued a new CM ID on a first-come basis.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
