Tuning the access to the LDAP server

Use the context pool parameters to improve the performance of concurrent access to an LDAP server.

The context pool is used in virtual member manager to improve the performance of concurrent access to an LDAP server. You can adjust the following parameters to improve the efficiency of the context pool:
maxPoolSize
Specifies the maximum number of live connections. If there is no available connection in the pool when request is submitted, the request waits the number of milliseconds specified in poolTimeOut. After this amount of time has passed, if no connection is available and the current number of live connections is less than the maxPoolSize, a new connection is created. If the total number of live connections is equal to or larger than maxPoolSize, an exception is thrown.

This parameter is mandatory for enabling the pool. If this parameter is not specified or specified with a value less than or equal to 0, the pool is disabled. If the pool is disabled, virtual member manager only reuses one connection.

initPoolSize
Specifies the minimum number of live connections. When the pool is initialized, this number of connections is created. The actual number of live connections changes depending on the number of concurrent requests.

The value of this parameter must be larger than 0 and, in general, less than 10. The default value is 1.

poolTimeOut
Specifies the number of milliseconds a request waits before throwing an exception when no available connections are in the pool and the number of current connections is at the maxPoolSize limit. If this parameter is set to 0 the waiting time is unlimited. The default value is 3000.
poolWaitTime
Specifies the number of seconds a connection can exist in the connection pool. When requesting a connection from the pool, if this connection already exists in the pool for more than the time defined by poolWaitTime, this connection is closed and a new connection is created for the request. After the connection is used it is returned to the pool.

If this parameter is set to 0, a new connection is created for each request and no connection are put into the pool for reuse. If this parameter is set to -1 or any negative number, the connection does not expire and is reused until the connection is turned off (for example by a firewall or a socket timeout). The default value is -1.

If the connection is turned off, virtual member manager waits for the connection to throw a communication exception and for a new connection to be created. To avoid the waiting time, you can set the poolWaitTime to a shorter time.

This parameter applies only if the connection pool is enabled.

Terms of use | Feedback
(C) Copyright IBM Corporation 2005. All Rights Reserved.
IBM virtual member manager 6.1