When I am running the simple client-server program to send a message, closing the server and then restart it, the server is accepting the junk values. Is there any way to solve this problem?? Actually I want to send the message from the client continuously after some interval and after some time when we forcibly close the server and restarts it, it should accept the packets sending by the client. I have also checked by using REUSEADDR but it was not working.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Are you calling UDT::startup() and UDT::cleanup() at appropriate points?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
-
2014-02-27
I also get this problem if my application crashes, thus cleanup can't be called. When I restart it sometimes I'm unable to bind to the port. This is in windows, should the SO_REUSEADDR socket option not be used to avoid this?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
When I am running the simple client-server program to send a message, closing the server and then restart it, the server is accepting the junk values. Is there any way to solve this problem?? Actually I want to send the message from the client continuously after some interval and after some time when we forcibly close the server and restarts it, it should accept the packets sending by the client. I have also checked by using REUSEADDR but it was not working.
Are you calling UDT::startup() and UDT::cleanup() at appropriate points?
I also get this problem if my application crashes, thus cleanup can't be called. When I restart it sometimes I'm unable to bind to the port. This is in windows, should the SO_REUSEADDR socket option not be used to avoid this?