You can specify the following types of global resource limits:

maximum-concurrent-connections

Specify the maximum number of client connections that can be established at any given time.

If the server already has the maximum number of connections established, then any new connection attempts from any clients are rejected until an existing connection is closed.

The default value of zero indicates that no limit is enforced.

maximum-concurrent-connections-per-ip-address

Specify the maximum number of client connections that can be established at any give time from the same client system.

If the server already has the maximum number of connections established from a given client, then any new connection attempts from that client are rejected until an existing connection from that client is closed. The server continues to accept connections from other clients that have not yet reached this limit.

The default value of zero indicates that no limit is enforced.

maximum-concurrent-connections-per-bind-dn

Specify the maximum number of client connections that can be established at any given time while authenticated as a particular user.

This property applies after the connection is established because the bind operation to authenticate the user happens after the connection is established rather than during the course of establishing the connection itself.

If a given user reaches the maximum number of connections, then any new attempt to authenticate as that user causes the connection performing the bind to be terminated.

Note:

This limit applies only to authenticated connections and isn't enforced for clients that haven't authenticated or for clients that have authenticated as the anonymous user.

The default value of zero indicates that no limit is enforced.

Any changes to the maximum-concurrent-connections and maximum-concurrent-connections-per-ip-address properties take effect only for new connections established after the change is made. Any change to the maximum-concurrent-connections-per-bind-dn property applies only to connections, including existing connections, that perform authentication after the change is made.

Existing connections are allowed to remain established even if that would cause the new limit to be exceeded.