ShowTable of Contents
Lotus Notes Traveler problems caused by an insufficient number of active HTTP threads
Lotus Notes Traveler devices utilize Domino web server HTTP threads when communicating with the server. If the number of active HTTP threads is insufficient, the following problems may occur:
- Apple device users may experience "Cannot connect to server" messages or slow responsiveness when opening, sending, or synchronizing email, contacts, or calendar items and when downloading email attachments
- Other device users may see error 503 (Server busy) messages in the Notes Traveler client interface, experience sync failures, and general slow responsiveness
- Server CPU and memory utilization may increase to abnormal levels
How to determine the number of active HTTP threads needed for Lotus Notes Traveler
The number of active HTTP threads needed for Traveler is calculated this way:
1.2 x Number of registered devices = Number of needed active HTTP threads
Default HTTP thread values activated by Lotus Notes Traveler
Lotus Notes Traveler will set the active HTTP threads to a default value depending on the architecture of the Domino instance.
For 32-bit Domino installations, 100 HTTP threads are allocated. This is done via the following notes.ini parameter, added automatically during Notes Traveler installation:
For 64-bit Domino installations, 400 HTTP threads are allocated. This is done via the following notes.ini parameter, added automatically during Notes Traveler installation:
These parameters are used to set the HTTP Number active threads
value in the Server document during Traveler startup if NTS_AUTO_CONFIG=true
is also present in notes.ini and the Traveler Server ID has appropriate ACL access to names.nsf.
How to determine the number of Notes Traveler devices
At the Domino console on the Traveler server, run the following command:
tell traveler stat show
In the output displayed by the command, find Push.Devices.Total
, which is the total number of devices registered with the server.
Push.Devices.Total = 225
This indicates that 225 devices are registered for synchronization with the Notes Traveler server. This number of devices indicates that at least 270 HTTP threads are needed (1.2 x 225 = 270).
If the console output is scrolling too quickly to find this information, the info can be dumped to a file by doing the following:
1. Run the console command tell traveler systemdump stat
2. Open \data\IBM_TECHNICAL_SUPPORT\traveler\logs\dumps\systemdump..log
3. Search for Push.Devices.Total
How to determine the current number of active HTTP threads
The current number of active HTTP threads allocated by the Domino web server at startup can be found in the Server document on the Internet Protocols -> HTTP
tab in the Number active threads
In the screenshot above, 100 active HTTP threads are allocated by the Domino web server during startup.
When using the systemdump file to find the current number of active HTTP threads, search for this setting:
For example, this would be the line as found in a systemdump:
Name: HTTP_MaxActiveThreads Type: Number/number list Size: 10 Value: 100
How to change the number of active HTTP threads
The number of active HTTP threads can be changed in the Server document on the Internet Protocols -> HTTP
tab in the Number active threads
After saving the change shown in the screenshot above and restarting the HTTP task, 270 active HTTP threads will be allocated by the Domino web server during startup.
To make this change effective, stop and restart HTTP (console command: restart task http
: Allocating too many active HTTP threads will result in unnecessary server memory consumption, so it is recommended to only allocate the necessary number of HTTP threads needed for proper Notes Traveler operation, as described here. If other HTTP applications are running on the Traveler server (for example, iNotes or Sametime), the number of threads needed for Lotus Notes Traveler will need to be added to the threads used by these applications.cs