You can specify the following types of global resource limits:
  • Specify the maximum number of client connections that can be established at any given time using the maximum-concurrent-connections property. If the server already has the maximum number of connections established, then any new connection attempts from any clients will be rejected until an existing connection is closed. The default value of zero indicates that no limit is enforced.

  • Specify the maximum number of client connections that can be established at any give time from the same client system using the maximum-concurrent-connections-per-ip-address property. If the server already has the maximum number of connections established from a given client, then any new connection attempts from that client will be rejected until an existing connection from that client is closed. The server may continue to accept connections from other clients that have not yet reached this limit. The default value of zero indicates that no limit is enforced.

  • Specify the maximum number of client connections that can be established at any given time while authenticated as a particular user with the maximum-concurrent-connections-per-bind-dn property. 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 the maximum number of connections are authenticated as a given user, then any new attempt to authenticate as that user will cause the connection performing the bind to be terminated. Note that this limit applies only to authenticated connections, and will not be enforced for clients that have not 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 will take effect only for new connections established after the change is made. Any change to the maximum-concurrent-connections-per-bind-dn property will apply only to connections (including existing connections) which perform authentication after the change is made. Existing connections will be allowed to remain established even if that would cause the new limit to be exceeded.