IBM Support

Traveler Devices cannot sync due to 503 errors and hung threads

Technote (troubleshooting)


Problem

Traveler users are unable to sync. The server status is red with several device sync failures because the server is too busy with a status of 503.

Symptom

The systemdump displays a similar message as below:
Yellow Status Messages
User <username> on thread <thread> has been running for 32 minutes.

Red Status Messages
There have been 1170 device sync failures because the server is too busy and returned status code 503.

The console command also displays the following messages:


Line 3836: [28174:00016-4165314304] 09/08/2014 11:51:30 AM HTTP JVM: 26764 [Traveler-InitConfig-f845a700] INFO - Multiple host addresses were found:
Line 3837: [28174:00016-4165314304] 09/08/2014 11:51:30 AM HTTP JVM: 26767 [Traveler-InitConfig-f845a700] INFO - <IP Address 1>
Line 3838: [28174:00016-4165314304] 09/08/2014 11:51:30 AM HTTP JVM: 26768 [Traveler-InitConfig-f845a700] INFO - <IP Address 2> (Selected)
Line 3839: [28174:00016-4165314304] 09/08/2014 11:51:30 AM HTTP JVM: 26769 [Traveler-InitConfig-f845a700] WARN - Address specified in notes.ini, NTS_HOST_IP_ADDR=<IP Address 2> is valid but is reported as not reachable.
Line 3840: [28174:00016-4165314304] 09/08/2014 11:51:30 AM HTTP JVM: 26771 [Traveler-InitConfig-f845a700] WARN - Notes Traveler will be allowed to start using this IP address, but you should verify network connectivity to the Notes Traveler server.


Cause

There are many threads attempting to access the localhost address unsuccessfully.


Diagnosing the problem

In review of the Traveler logs and systemdump, the following condition can be seen for threads that are hung:



--- Thread Details (107) (Mon Sep 08 15:39:03 EDT 2014) ---
DS-31f7d700[VrDZFgAA][2] [username] [device] [1 runnables] [Busy? true] [Last Runnable: Mon Sep 08 15:15:04 EDT 2014] [Running: 1439311ms] [Idle: 451ms] Notes Inited(C,J)=(true, true)

When searching for the hung thread, DS-31f7d700[VrDZFgAA][2], it is displayed with the following condition:

DS-31f7d700[VrDZFgAA][2] (DS-31f7d700[VrDZFgAA][2] [1 runnables] [Busy? true] [Last Runnable: Mon Sep 08 15:15:04 EDT 2014] [Running: 1439338ms] [Idle: 451ms] Notes Inited(C,J)=(true, true)) (ID=193) (State=BLOCKED) (CPU (Total): 835ms) (CPU (User): 835ms) (Suspended: false) (In Native: false) (Locked: java.net.InetAddress$localHostCacheLock@7320732 held by Worker-39b96700 which has ID 141) (Waited: 22 times for unknown ms) (Blocked: 1 times for unknown ms) (Monitors Held: None) (Synchronizers Held: None)
java.net.InetAddress.getLocalHost(InetAddress.java:1508)
javax.mail.internet.InternetAddress.getLocalAddress(InternetAddress.java:503)
javax.mail.internet.UniqueValue.getUniqueMessageIDValue(UniqueValue.java:93)
javax.mail.internet.MimeMessage.updateMessageID(MimeMessage.java:1991)
javax.mail.internet.MimeMessage.updateHeaders(MimeMessage.java:2014)
javax.mail.internet.MimeMessage.saveChanges(MimeMessage.java:1980)
javax.mail.internet.MimeMessage.writeTo(MimeMessage.java:1680)

Resolving the problem

This type of response indicates a problem in the network. By default, the Traveler server's IP address is looked up on each call. The following JVM option can be used to cache the lookup after the first time.

1. Add the parameter NTS_JAVA_PARMS=-Dcom.ibm.cacheLocalHost=true

2. Restart the Traveler Server to have the change effect.

After the restart, users should begin to sync successfully.

Document information

More support for: IBM Traveler
Performance

Software version: 8.5.3, 9.0, 9.0.1

Operating system(s): Linux, Windows

Reference #: 1684613

Modified date: 22 September 2014


Translate this page: