The document discusses common issues that Travelers users complain about and provides solutions. It addresses issues like latency between Traveler and mail, a stuck Traveler servlet, insufficient HTTP threads, constraint mode being triggered, servers only showing as 50% available, and database performance problems. Solutions provided include checking network connections, restarting components, increasing resources like threads and memory, and performing regular database maintenance.

1. Kris De Bisschop
Help, my Travelers complain about performance, what to do ??

2. A little about me
2
• CEO GroupWave
• Administrator ICS Portfolio
o IBM Notes/Domino
o IBM Sametime
o IBM Notes Traveler
o IBM Connections
o TDI
• Social Business speaker
• Love high-level issues
• Badminton

3. Where are we ?
3
• Traveler 9.0.1.14 has been released on 7th of september
o Release notes can be found here
• Downloads of FP for Windows, Linux, IBMi here
• Full version available in PA as of 14th of september

4. Setup Standalone
4

5. Setup Cluster
5

6. Server status
• tell traveler status
• gives a first indication
• Traveler’s self assessment of health
6

7. Server status
• Sh stat traveler.status.*
• Displays more detail about the status
• Indication where to check for issue
7

8. Issue #1: Latency between
Traveler and Mail
• Traveler and Mail Server on different networks
• Check Network quality
• WAN ? VPN ? Other ?
• Use tools like WireShark for troubleshooting
8

9. Issue #2: Traveler Servlet stuck
• Symptoms
• Issues with authentication against the
Traveler page
• Users cannot sync with the Traveler
9

10. Issue #2: Traveler Servlet stuck
• How to fix ?
• Tell traveler quit / load traveler
• Check memory/CPU usage on server
10

11. Issue #3: Insufficient HTTP
Threads
• Initial configuration <> growth of usage
• Smartphones / tablets
• 1 device = 1 thread
• Max number of threads is set in server doc
• 400 threads is default value 64-bit server
• Needed threads= 1,2 x #devices
11

12. Issue #3: Insufficient HTTP
Threads
• Symptons
• Sync failures
• Slow responsiveness
• Apple users get “Cannot connect to server”
12

13. Issue #3: Insufficient HTTP
Threads
• How to fix ?
• Check number of devices
• Command: show stat Traveler.Push.Devices.Total
• Output : Push.Devices.Total = xxx
• Check number of threads
• show stat http.workers
• http.workers = xxx
13

14. Issue #3: Insufficient HTTP
Threads
• How to fix ?
• Increase number of HTTP Threads
14

15. Issue #3: Insufficient HTTP
Threads
• How to fix ?
• Check max number of concurrent connections
• Restart HTTP
15

16. Issue #4: Constraint Mode
• Symptoms
• Traveler doesn’t allow new devices to sync/prime sync
• Existing users continue to sync
• Same connectivity error as in HTTP Thread issue
• system memory or database connections exceed a threshold
16

17. Issue #4: Constraint Mode
• How to fix ?
• Check constraint mode status
• show stat Traveler.Constrained.State
• Value 1 = constraint mode
• Value 0 = normal mode
• Self-healing
• exits constraint mode when memory usage is 5% below Red level
17

18. Issue #4: Constraint Mode
• How to fix ?
• Short-term
• Restart the server
• Long-term
• Increase physical RAM
• Increase JVM RAM
18

19. Issue #5: 50% available in stead
of 100%
• Clustered Traveler Servers can be set in off state
• Tell Traveler Available Off
• After maintenance, you have to set it back
• Tell Traveler Available On
• Tell Traveler HADR Show
19

20. Issue #6: Database performance
• Symptoms
• More devices get connected
• More data gets stored
• Database grows in size
20

21. Issue #6: Database performance
• How to fix ?
• Defragmentation of database once a month
• Manual defragmentation
• Tell Traveler Quit
• Tell HTTP Quit
• Load Traveler -defrag
21

22. Issue #6: Database performance
• Running defragmentation on a scheduled basis
• 8.5.3.1 to 9.0.1.7
• Add NTS_DEFRAG_INTERVAL_DAYS to the notes.ini file
• 9.0.1.8 and later
• tell traveler dbmaint set interval xx
• tell traveler DBMaint set auto on
• Force with tell traveler dbmaint run
22

23. 23
OR
Hungry !!!

24. Contact
24
https://www.linkedin.com/in/debisschopk
@debisschopk
https://debisschopk.wordpress.com/
kris.de.bisschop@groupwave.be