Client Socket and connection problem
-
Hi there, I was wondering if you have a client socket that is supposed to initiate the connection to a server, how often the client sends the request? I have a client socket and it seems that there is some wireless communication problem so that the socket connection to the server goes down and the client socket sends the request for connection every 1/100 second. Does it make sense to you guys? I log every messages that go through the sockets and I see the connection request every 1/100second and it seems that the connection is establishing and then I see WSAENOTSOCK message and the socket gets closed and the establishes and I get WSAECONNRESET message and it continues until the connection stays up and open. Does anybody know whatis going on here?? Thanks,
-
Hi there, I was wondering if you have a client socket that is supposed to initiate the connection to a server, how often the client sends the request? I have a client socket and it seems that there is some wireless communication problem so that the socket connection to the server goes down and the client socket sends the request for connection every 1/100 second. Does it make sense to you guys? I log every messages that go through the sockets and I see the connection request every 1/100second and it seems that the connection is establishing and then I see WSAENOTSOCK message and the socket gets closed and the establishes and I get WSAECONNRESET message and it continues until the connection stays up and open. Does anybody know whatis going on here?? Thanks,
It depends on the protocol. If you're using TCP then you could research the TCP protocol and see how it handles reconnects. I suppose that could be implementation specific - Microsoft's TCP implementation may be different then others. How are you seeing the socket error codes? These aren't part of the protocol. The WSAENOTSOCK error isn't good - that's usually (always?) from a programming error. Mark
"Great job, team. Head back to base for debriefing and cocktails." (Spottswoode "Team America")
-
It depends on the protocol. If you're using TCP then you could research the TCP protocol and see how it handles reconnects. I suppose that could be implementation specific - Microsoft's TCP implementation may be different then others. How are you seeing the socket error codes? These aren't part of the protocol. The WSAENOTSOCK error isn't good - that's usually (always?) from a programming error. Mark
"Great job, team. Head back to base for debriefing and cocktails." (Spottswoode "Team America")
I have done this t get the Error: BOOL Socket::StoreError( INT Error ) { BOOL RetCode; RetCode = FALSE; __try { if( Error != 0 ) { ......... switch( Error ) { case WSAEACCES: wsprintf( ErrBuff, "WSAEACCES" ); break; case WSAEADDRINUSE: wsprintf( ErrBuff, "WSAEADDRINUSE" ); break; case WSAENOTSOCK: wsprintf( ErrBuff, "WSAENOTSOCK" ); break; ........... ........... if(( strlen( ErrBuff )> 0 )&&( RetCode )) { LogError( "Socket", "StoreError", "%s, %s", sName, ErrBuff ); } I also check the status of the socket in the data link layer and write it down to the log.
-
I have done this t get the Error: BOOL Socket::StoreError( INT Error ) { BOOL RetCode; RetCode = FALSE; __try { if( Error != 0 ) { ......... switch( Error ) { case WSAEACCES: wsprintf( ErrBuff, "WSAEACCES" ); break; case WSAEADDRINUSE: wsprintf( ErrBuff, "WSAEADDRINUSE" ); break; case WSAENOTSOCK: wsprintf( ErrBuff, "WSAENOTSOCK" ); break; ........... ........... if(( strlen( ErrBuff )> 0 )&&( RetCode )) { LogError( "Socket", "StoreError", "%s, %s", sName, ErrBuff ); } I also check the status of the socket in the data link layer and write it down to the log.
Ok, but what calls this Socket::StoreError() method? If you are getting a WSAENOTSOCK error somewhere then that means a socket op is being attempted on a handle (SOCKET) which isn't a known socket. Not good :)
"Great job, team. Head back to base for debriefing and cocktails." (Spottswoode "Team America")
-
Ok, but what calls this Socket::StoreError() method? If you are getting a WSAENOTSOCK error somewhere then that means a socket op is being attempted on a handle (SOCKET) which isn't a known socket. Not good :)
"Great job, team. Head back to base for debriefing and cocktails." (Spottswoode "Team America")
One other question, 1. Let say my socket is connected to the server 2. I turn off the wireless link of my computer and there should be no socket connection. 3. Neither client socket nor server socket understand that the connection is gone until I re connect the wireless switch in my computer and get connected to the network, at that time my application sees the connection went down and came back up. And it is the time that sometimes I see those error messages until I restart one of the application and have the socket connected again. What do you think?
-
One other question, 1. Let say my socket is connected to the server 2. I turn off the wireless link of my computer and there should be no socket connection. 3. Neither client socket nor server socket understand that the connection is gone until I re connect the wireless switch in my computer and get connected to the network, at that time my application sees the connection went down and came back up. And it is the time that sometimes I see those error messages until I restart one of the application and have the socket connected again. What do you think?
I think then that the connection is closed and needs to be reconnected. That would explain the NOTSOCK error since the socket became invalid at some point. That also explains the WSAECONNRESET error. When you get that error the connection is closed. That means you should close the socket and reconnect.
"Great job, team. Head back to base for debriefing and cocktails." (Spottswoode "Team America")
-
I think then that the connection is closed and needs to be reconnected. That would explain the NOTSOCK error since the socket became invalid at some point. That also explains the WSAECONNRESET error. When you get that error the connection is closed. That means you should close the socket and reconnect.
"Great job, team. Head back to base for debriefing and cocktails." (Spottswoode "Team America")
The NOTSOCK error is because somewhere in your code you are closing the socket handle. If the wireless connection gets down, in a period of time you will receive de connection reset error when the system detects the broken connection but the socket handle still remains valid so you should not receive notsock errors unless you closed the handle. Best regards, Mauro.
-
The NOTSOCK error is because somewhere in your code you are closing the socket handle. If the wireless connection gets down, in a period of time you will receive de connection reset error when the system detects the broken connection but the socket handle still remains valid so you should not receive notsock errors unless you closed the handle. Best regards, Mauro.
Good point. Something is happening to the socket somewhere, but we haven't seen any code so who knows? Thanks! Mark
"Great job, team. Head back to base for debriefing and cocktails." (Spottswoode "Team America")
-
Good point. Something is happening to the socket somewhere, but we haven't seen any code so who knows? Thanks! Mark
"Great job, team. Head back to base for debriefing and cocktails." (Spottswoode "Team America")
-
The NOTSOCK error is because somewhere in your code you are closing the socket handle. If the wireless connection gets down, in a period of time you will receive de connection reset error when the system detects the broken connection but the socket handle still remains valid so you should not receive notsock errors unless you closed the handle. Best regards, Mauro.