Tuning access to the LDAP server in a Sametime Advanced deploymentAdded by IBM on November 23, 2011 | Version 1 (Original)
|Set the context pool parameters to improve the performance of concurrent access to an LDAP server.
Set the context pool parameters to improve the performance of concurrent access to an LDAP server.
About this task
The context pool is used in virtual member manager to improve the performance of concurrent access to an LDAP server. Use the Integrated Solutions Console on the Deployment Manager. You can also edit values in the wimconfig.xml file stored here:
The following instructions contain settings that were tested in IBM labs. Adjust these settings as needed for your specific environment.
Parent topic: Tuning WebSphere Application Server in a Sametime Advanced deployment
- In the Integrated Solutions Console for the Deployment Manager, click Security -> Global security.
- Under User account repository, select Federated repositories from the Available realm definitions field and click Configure.
- Under Related items, click Manage repositories.
- Select the configured LDAP repository.
- Under Additional properties, click Performance.
- Set the following context pool parameters:
|Maximum size (maxPoolSize): 200||Specifies the maximum number of live connections. If there is no available connection in the pool when the 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.|
|(Can be set only in the wimconfig.xml file) poolWaitTime="5000"||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.
|Preferred size (prefPoolSize): 20||Specifies the preferred number of context instances that the context pool will maintain. Context instances that are in use and those that are idle contribute to this number. When there is a request for the use of a pooled context instance and the pool size is less than the preferred size, the context pool creates and uses a new pooled context instance regardless of whether an idle connection is available. When a request finishes with a pooled context instance and the pool size is greater than the preferred size, the context pool closes and removes the pooled context instance from the pool.|
The valid range for this parameter is from 0 to 100. Setting the value of this parameter to 0 means that there is no preferred size and a request for a pooled context instance results in a newly created context instance only if no idle ones are available. The default value is 3.
|Cache the attributes Cache size: 80000||Specifies the number of LDAP attributes that are cached by the server.|
|Cache the search results Cache size: 80000||Specifies the number of LDAP search results that are cached by the server.|
- Save the changes.