Backward compatibility and limitations
The enhanced connection pool optimizes database connectivity by dynamically scaling connections based on workload, reusing connections for rapid client operations, and automatically monitoring connection health.
Backward compatibility
The Enhanced Connection Pooling feature is fully backward compatible. Existing ibmslapd.conf files that do not include the new parameters continue to work without modification. In this case, the following defaults are applied automatically:
| Parameter | Default (if not specified) |
|---|---|
ibm-slapdDbMinConnections |
25 % of ibm-slapdDbConnections, with a minimum of 5 |
ibm-slapdDbMaxConnections |
Same as ibm-slapdDbConnections |
ibm-slapdDbConnectionTTL |
3600 seconds (1 hour) |
ibm-slapdDbHealthCheckInterval |
10 seconds |
ibm-slapdDbConnectionHoldTime |
0 seconds |
Command-line administration tools such as ldif2db, db2ldif, idsrunstats, and idbulkload are not affected by enhanced connection pool parameters. These tools use a single dedicated database connection and do not start the background health check thread.
Changes to connection pool configuration parameters require a server restart to take effect. Dynamic reconfiguration of connection pool settings is not supported in this release.
Limitations
The following limitations are relevant to the enhanced connection pool in this release.
| Limitations | Description |
|---|---|
| Server restart required | Changes to any connection pool parameter require a server restart to take effect. Dynamic reconfiguration is not supported. |
| Pool statistics not in Web Administration UI | The connection pool monitoring attributes described above are accessible only through ldapsearch against cn=monitor. They are not yet surfaced in the IBM Verify Directory Web Administration console. |
| Hold time not adaptive | The hold time value is a single global setting. Per-connection-type or automatically tuned hold times are not supported in this release. |
| Maximum pool size | The maximum value for ibm-slapdDbMaxConnections is 999. Configurations requiring more than 999 simultaneous database connections are not supported. |