TCP connect issue
Issue #34
resolved
From Richard,
The timeout in the REmoteTCPMessenger.lvclass:Create.vi is too short. This has taken me a while to debug (notice the time!) but 3 seconds is not sufficient. It appears the "Get LabVIEW Version" method inside is responsible for the delayed reply. I had to increase the 3000 to 8000 to get a successful connection: image.png
Comments (8)
-
repo owner
-
repo owner
Problem appears to be that I have added a negotiation of common LabVIEW version, needed for supporting different LabVIEW versions on each side. If this takes a long time (and can if the Connection started on the server side takes a long time to start), then it will use up the 3000 ms of extra time. This also assumes the actual TCP connection uses most of it’s “timeout ms”.
-
repo owner
I’m thinking of just not having a timeout here at all, and instead put a (long) timeout on the TCP read in the Version negotiation (followed by a meaningful error message if it fails).
-
repo owner
Default TCP Connection timeout is only 5 seconds, which is quite short, compared with the TCP primitive that uses 60 seconds!
-
repo owner
-
repo owner
Increased default “Connection Timeout” to 15000 ms from 5000
Changed the added timeout to +30000 ms (really, could have infinite timeout).
for Version 1.11.2
-
repo owner
Note: TCP Server creation timeout is 10000 ms, which maybe should be higher (but not changing it).
-
repo owner
- changed status to resolved
- Log in to comment
