IBM Tivoli Directory Integrator
Specifying a reconnect rule is necessary for a reconnect to be
attempted. However it is not sufficient by itself. The other requirement
is enabling reconnect in the general reconnect configuration. This
can be done under the Connection Errors tab
in the Configuration Editor . If reconnect is not enabled in this
configuration, reconnect is not attempted in case of error regardless
of the decision of the Reconnect Rule Engine. Here is a list of Configuration
options:
- Number Of Retries
- The number of times a reconnect attempt is made when a problem
occurs, before giving up. If a new problem occurs later on, the same
number of attempts is made.
- Delay Between Retries
- The number of seconds to wait between each reconnect attempt, and before the first reconnect attempt.
- Retry Connect on Initial Connection Failure
- If this flag is set, and a connection cannot be established
when the connector is being initialized, a "reconnect" attempt is
made. Not really reconnect, since a connection was not established
in the first place, but generally the same mechanism.
- Auto Reconnect on Connection Loss
- If this flag is set, and the connection is lost after the connector
is initialized, a reconnect attempt is made.
- Auto Skip Forward
- After a reconnect, automatically skip forward as many times
as the number of successful reads.
For both the Retry
Connect on Initial Connection Failure and Auto
Reconnect on Connection Loss flags, the reconnect engine is determine
if the exception leads to a reconnect attempt, or is a more general
error.