Troubleshoot Search-related memory issues

Overview

If the Search application is installed on a different server from the Connections applications, we can enable the following memory monitoring counters in LotusConnections-config.xml.

Counter	Description
Active transactions	Number of active transactions waiting for a response from the Search server.
Queue	Number of active transactions queuing to connect to the Search server.

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 LotusConnections-config.xml, 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

We can set the limits allowed by the active transactions counter and the queue counter by configuring settings in LotusConnections-config.xml.

Configure memory settings

1. Check out Connections configuration files:
   cd app_server_root/profiles/Dmgr01/bin
   ./wsadmin.sh -lang jython.
   execfile("connectionsConfig.py")
   LCConfigService.checkOutConfig("/tmp","cell_name")

   To determine cell:

   print AdminControl.getCell()

2. Edit LotusConnections-config.xml

3. 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>

4. 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>

5. Save the changes and then check the configuration files back in :

   LCConfigService.checkInConfig()

   Run the checkin during the same wsadmin session in which you ran the checkout command.

6. To exit the wsadmin client, type exit at the prompt.

7. Stop and restart all of the Connections application servers.

Parent topic:
Troubleshoot Search

Related:

Start the wsadmin client