If you are experiencing higher than normal CPU utilization with Lotus Notes Traveler, you should first open a PMR on the issue to determine if there is an underlying problem. To do so:
- Start Tracing on the Lotus Notes Traveler server:
Tell Traveler log level finest
Tell Traveler log count 100
- Verify that the problem occurs.
- Initiate a system dump:
- Wait 5 or 10 minutes , then initiate a second system dump, as in step 3.
- Wait for the system and NSD dumping to finish.
- Collect the logs and send to IBM:
Tell Traveler log collect
Upload <DominoData>/IBM_TECHNICAL_SUPPORT/traveler/logs/<DatedFolder from step 6>
For a possible work around, you can also try to defragment the Lotus Notes Traveler database. It is best to do this during a scheduled outage, since the process could take 30 minutes or more to complete, depending on your system.
- Shut down Lotus Notes Traveler:
Tell Traveler Shutdown
Tell HTTP Quit
- Wait for Lotus Notes Traveler to shutdown completely, otherwise the defragmentation will fail. If Lotus Notes Traveler does not shutdown after a reasonable amount of time, issue the command "Tell Traveler Quit".
- Once Lotus Notes Traveler is shut down, restart it using the "defrag" parameter:
- After Traveler restarts, verify that HTTP has also started. If not, issue the command "Load HTTP".
- Your system should be back up and running. Monitor the CPU to see if the defragmentation fixed the problem.