Traveler 8.5.1 error. Time out error?

Getting this error with Traveler. Using iPhone. Ideas how to cure?

Seems to work otherwise though, based on what I see.

10/13/2009 01:41:54 PM HTTP JVM: Traveler: Lotus Traveler task did not respond within the allotted time frame. Client request denied for CN=John Smith/O=ACME

Subject: Traveler timeout

Unfortunately have not seen that problem before. If persistent it may be worth contacting IBM support and opening a Problem Report to all review of the configuration and log data.

Thanks.

Subject: I got the same problem

running on 64 bit windows. wonder if that’s the problem?

Subject: Actually

after going to calendars and opening the traveler one and then back to mail made it work. nice.

Subject: Same here

Get the message after HTTP authentication with the server from a web browser.Also 64-bit Windows 2008 server with Domino 8.5.1 and Traveler 8.5.1

Have raised a PMR with Support.

Previous test install on W2003/Dom8.5/Traveler 8.5 worked fine…

Subject: Resolved

In my case it turned out to be an issue with the internal Traveler ports (50125 & 50126). Basically they were listening on different IPs (you can confirm this by running a netstat -a on the server). Hardcoding them in the Notes ini using the following parameters and restarting the server resolved it:

NTS_IPC_TCP_Port=50125,<name/ip>

NTS_IPC_TCP_Port2=50126,<name/ip>

where <name/ip> is the local ip address or name (localhost, FQDN)

For info support also informed me that the ports do the following:

50125 is ntraveler.exe listening for HTTP connections

50126 is HTTP listening for connections from ntraveler.exe

Subject: it works

I had same problem with Traveler on 8.5.1, this solution also works for me!

Thank you.

Subject: Another solution (?)

I still have the same problem, sporadically but frequently. It never happened with the beta version though. I then ran across this: http://www.bleedyellow.com/blogs/bskedel/entry/traveler_8_5_1_performance_documentation_has_an_error3?lang=en_us which suggested changing a line in servlet.properties from servlet.traveler.initArgs=ntstimeoutsyncas=230 to 230000. That line doesn’t exist in the beta version, which may be why I wasn’t seeing the problem there? I haven’t had it running long enough after the change to know if this is going to resolve the problem though.

Subject: RE: Another solution (?)

If you are still using 8.5.1, then the line isn’t there by default. The documentation tells you how to add it (and other considerations/changes to make).

The link you provided was because the documentation was wrong (230 instead of 230000) for some period of time (it is fixed now). The unit is milliseconds, so 230ms was way too short - it needs to be 230000ms which is 230 seconds.

If you have upgraded to 8.5.2, most of those settings got removed from servlets.properties (to make it easier to configure correctly by only changing one value instead of two), so that would also be why you wouldn’t find it. But if you are on 8.5.1 which this thread is talking about, you would want it. Otherwise, you need to open a PMR for logs to be collected and analyzed.

Subject: Resolved with Notes.ini-Parameters

I solved the problem with the following two Notes.ini parameters:NTS_IPC_TCP_Port=50125,

NTS_IPC_Servlet_TCP_Port=50126,

Subject: RE: Resolved

While you can specify these options in notes.ini, they are also on the Lotus Traveler tab in the server document. The Notes.ini parameters override the server document value, so if you switch to the Lotus Traveler tab, you will need to remove the notes.ini parameters. If not, just remember that the server document setting for the ports is being overwritten by the notes.ini parameters.

We have these settings to handle odd IP setups, so I’m glad that it worked as intended.