Traveler Task has not responded in allotted timeframe

After a server restart today, many of the iPhone users are not able to connect to the traveler server. The server log shows Lotus Traveler task did not respond in allotted timeframe. Client request denied for…This is not happening to all users. Some users are fine, others can’t connect at all, and yet others it is hit or miss on. Any thoughts on what is causing this? I already opened a PMR with IBM.

Subject: Problem solved

I had followed the performance tuning of the server document:

http://publib.boulder.ibm.com/infocenter/domhelp/v8r0/index.jsp?topic=/com.ibm.help.lnt851.doc/Tuning_performance_of_the_server.html

Unfortunately, the documentation is not correct and IBM will open a defect to have it corrected.

AS_REQUEST_TIME_LIMIT is correctly stated as being in seconds. However, ntstimeoutsyncas is in milliseconds, not seconds.

Thus, the servlet is only waiting 230ms for the traveler process to respond. That is such a short period of time that you are going to see that timeout very, very often.

You should change ntstimeoutsyncas to be 230000 instead of 230 in servlets.properties.