9.2. Detecting Errors During Normal Processing
nsMaxTestResponseDelay— which work together to determine if the remote server is no longer responding.
nsMaxResponseDelay, sets a maximum duration for an LDAP operation to complete. If the operation takes more than the amount of time specified in this attribute, the database link's server suspects that the remote server is no longer online.
nsMaxResponseDelayperiod has been met, the database link pings the remote server. During the ping, the database link issues another LDAP request, a simple search request for an object that does not exist in the remote server. The duration of the ping is set using the
nsMaxTestResponseDelayperiod has passed, then an error is returned, and the connection is flagged as down. All connections between the database link and remote server will be blocked for 30 seconds, protecting the server from a performance degradation. After 30 seconds, operation requests made by the database link to the remote server continue as normal.
cn=config,cn=chaining database,cn=plugins,cn=configentry. The following table describes the attributes in more detail:
Table 9.2. Database Link Processing Error Detection Parameters
|nsMaxResponseDelay|| Maximum amount of time it can take a remote server to respond to an LDAP operation request made by a database link before an error is suspected. This period is given in seconds. The default delay period is |
|nsMaxTestResponseDelay|| Duration of the test issued by the database link to check whether the remote server is responding. If a response from the remote server is not returned before this period has passed, the database link assumes the remote server is down, and the connection is not used for subsequent operations. This period is given in seconds. The default test response delay period is |