Monitoring Data Sources by Testing Established Connections

When this type of monitoring is configured, Directory Proxy Server tests each connection to each data source at regular intervals. In this way, the proxy prevents connections from being dropped because of inactivity, and detects closed connections.

This type of monitoring can be used in addition to Monitoring Data Sources by Periodically Establishing Dedicated Connections.

Directory Proxy Server can be configured to test connections in the following scenarios:

• Pooled connections that are not used for a period of time

• Connections for persistent searches that are not active for a period of time

• Connections between a client and Directory Proxy Server operating in tunneling mode

Testing established connections consumes system resources, but it provides good security for connections. If you are using the Active Directory product, you must use this method of monitoring because the Active Directory product closes inactive connections.

To test an established connection, Directory Proxy Server issues a search request with the following parameters:

• Search base DN

• Connection time out

• Search time out

• Search filter

If a connection is found to be down, Directory Proxy Server polls the connection at a specified interval to detect its recovery. You can configure this interval by setting the monitoring-interval property. For more information, see To Monitor a Data Source by Testing Established Connections in Sun Java System Directory Server Enterprise Edition 6.0 Administration Guide.

Directory Proxy Server monitors data sources by using a search filter. Data sources that return a result that satisfies the filter are considered to be working.