tcp error 60 on singleboard rio

[giac82]

i'm developing a remote server on my single board rio.

the server runs in back ground.

after the connection with the client is lost or the stop button is pushed, the server stops its execution.

after a time delay the server vi is recalled and runned.

after few iteration the error 60 on create listener occours.

the same application runs well, if both client and server are on my PC.

[MikeS81]

Hi giac82,

do you close the connection reference after the connection is lost? You should do it, if not then maybe this port is not freed by the system and stays in use and that's what error 60 shows.

Mike

[giac82]

yes i close the connection. i also can tell you that after the tcp close block is executed the connection reference isn't still valid as i assumed. maybe i have to wait xxx seconds before closing the server vi to allow the close connection to take effect?

[MikeS81]

Hi giac82,

do you close it on both sides?

Mike

[giac82]

yes i close the connection on both sides.

[giac82]

now i'm trying to run a simplified version of the server.

the problem is still present, but the failure rate is decreased.

what seems to me is that there is a dependecy from the "size" of code and the target machine.

on my PC the full version runs well.

on single board RIO the full version has a high failure rate

on single board RIO the simplified version has  a low failure rate.

is it possible?

[giac82]

the latest experiments give results in contradiction with what i wrote above.

the server (full or simplified) gives error 60 if stopped and restarted on the single board rio side where it is running.

if the connection is closed by the client, the server restarts without errors.

is it possible that the sb-rio doesn't close correctly the connection because the client still has activity on the port, while closing?