Troubleshooting Search-related memory issues
You can configure settings in the LotusConnections-config.xml file to avoid out-of-memory issues or other problems caused by long response times from the Search application.
Before starting
To edit configuration files, use the IBM WAS wsadmin client. See Starting the wsadmin client for details.
About this task
In a heavily-loaded environment or when IBM Connections is deployed in an environment with inadequate hardware, the applications that use Search can get blocked while waiting for search results. They can also run out of memory if the Search application is overloaded with hanging threads or transactions that have not completed.IBM Connections provides two counters that ensure that the applications using Search do not get blocked, and that they can resume normal behavior without administrative intervention once the Search application is operating properly again. These two counters act as a mechanism to determine if the Search server is able to accept new connections.
Active transactions counter
Counts the number of active transactions that are waiting for a response from the Search server.
Queue counter
Counts the number of active transactions that are queuing to connect to the Search server.
Note: These counters only work when the Search application is installed on a different server from the IBM Connections applications.
The active transactions counter allows a specified number of active transactions to wait for a response from the Search server. For example, if the limit is set to 20, when 20 active transactions are waiting for a response from the Search server, any subsequent attempts to connect to the server are placed in a queue. If the queue counter is not equal to the value defined in the LotusConnections-config.xml configuration file, the connection to the Search server is rejected. If the queue counter is equal to the value set in the configuration file, a connection to the server is allowed. If the Search server returns data without an timeout exception being returned to the application, the queue counter is reset to 0.
You can set the limits allowed by the active transactions counter and the queue counter by configuring settings in the LotusConnections-config.xml file.
Procedure
- From the dmgr host:
cd $DMGR_PROFILE/bin
./wsadmin.sh -jython
execfile("connectionsConfig.py")If prompted to specify a service to connect to, type 1 to pick the first node in the list. Most commands can run on any node. If the command writes or reads information to or from a file using a local file path, pick the node where the file is stored. This information is not used by the wsadmin client when you are making configuration changes.
- Check out the IBM Connections configuration files:
LCConfigService.checkOutConfig("<working_directory>","<cell_name>")
where:
- <working_directory> is the temporary working directory to which the configuration XML and XSD files are copied and are stored while you make changes to them. Use forward slashes to separate directories in the file path, even if you are using the Microsoft Windows operating system.
AIX and Linux only: The directory must grant write permissions or the command does not run successfully.
- <cell_name> is the name of the WAS cell hosting the IBM Connections application. This argument is case-sensitive, so type it with care. To obtain the cell name:print AdminControl.getCell()
For example:
- AIX or Linux:LCConfigService.checkOutConfig("/opt/temp","foo01Cell01")
- Microsoft Windows:LCConfigService.checkOutConfig("c:/temp","foo01Cell01")
Open the LotusConnections-config.xml in a text editor. Update the number of active transactions allowed by the active transactions counter by changing the value of the Transaction_Max property.
For example:
<attribute key="Transaction_Max" value = 20>
Update the number of active transactions allowed to queue by the queue counter by changing the value of the Queue_Max property.
For example:
<attribute key="Queue_Max" value = 10>
Save your changes and then check the configuration files back in using the following command:
LCConfigService.checkInConfig()
Note: You must run the checkin during the same wsadmin session in which you ran the checkout command.
To exit the wsadmin client, type exit at the prompt. Stop and restart all of the IBM Connections application servers.
Parent topic
Resolving a problem
Related tasks
Starting the wsadmin client
});