Problems With Exceptions and Sockets

Camon Zixahourz

I want to implement a TCP Listener wich Listens for 1 min if there is no connection pending i want to restart the whole process of creating the listener, this is because i'm implementing a state machine. try { do { retry = false; char[] mensaje = SMS.BuildMessageforRemota(name,destnum, port); //SMS.SendMessage(mensaje); //Making the TCPListener to Listen MyListener.Start(); myTimer.Change(0, 60000); Server(MyListener.AcceptSocket()); //if this is succesfully a blocking call then program flow //will be hold here until i have someone that has connected //or the Timer Stops the Listener } while (retry && attempts < 3); the routine wich is called by my timer: public void ResetConnectionAttemp(Object State) { attempts++; //increase the amount of attempts retry = true; if (MyListener != null) { MyListener.Stop(); } } now, when i call MyListener.Stop(), i get a SocketException because i make an unblocking call to the BlockingCall made by MyListener.AcceptSocket(), is there a way to avoid this exception, because this is exactly what i want to make, hold the program execution for 1 min, then stop it, and resend the SMS to wakeup whoever is going to connect with me,(if it doesn't works the first time, is because the message didn't arrive, that's why i need to resend it), another option is, is there a possibility to make a timeout for the listener, wich will close the connection by itself without throwing the exception without the Timer class?? thanks!!!

4 Replies

Know the answer? Post it — somebody with the same question will find it here.

Camon Zixahourz21y ago
thks , actually what i came to do, is the following, i placed a ManualResetEvent wich will signal with my main thread,while it is waiting, the Timer event will set the ManualResetEvent wich will allow program flow to continue on the main thread, on the other hand, instead of calling a Synchronous call to TCPListener.AcceptSocket(), i made it through and async call with TCPListener.BeginAcceptSocket(ASyncCallback,Object State), wich will handle the listening, and the process of dealing with the connection. :-)
+1
Andrei Arugay21y ago
Just give an idea here, i just got it in the MSDN 2003. I think its just similar to ConnectionTimeout on connecting to database 1. //Send operations will timeout of confirmation is not received within 1000 milliseconds. s.SetSocketOption(SocketOptionLevel.Socket, SocketOptionName.SendTimeout, 1000); 2. //Socket will linger for 10 seconds after close is called. LingerOption lingerOption = new LingerOption(true, 10); s.SetSocketOption(SocketOptionLevel.Socket, SocketOptionName.Linger, lingerOption); 3. // Allows a queue of 10 connections. aSocket.Listen(10); if (!aSocket.Connected) { Console.WriteLine("Winsock error: " + Convert.ToString(System.Runtime.InteropServices.Marshal.GetLastWin32Error())); }
+1
Camon Zixahourz21y ago
it is triggered by a Timer Event, it goes off every min , although i'm more interested in avoiding the socketexception thrown when i call the Stop method of myListener,
+1
Andrei Arugay21y ago
I notice dat u didn't place the method ResetConnectionAttempt() before the while() loop or just u didn't palce at this message or it is an event. Maybe u can check if the state of the Listener if its connected or not.
+1