Fastream Technologies wrote: > Let me clarify: I have the Send() function noticing an error in the > socket and calling OnSessionClose.
This is nothing a component user must handle, it's encapsulated in the the component. > Now at this point, I am currently > not calling Shutdown(), is this correct? Correct, since the connection already is gone, ShutDown() initialized a bidirectional shutdown ping-pong on an already died connection. > > The reason I am asking this is because when keep-alive is enabled on > the server side with a idle timeout, HTTP keep-alive or Winsock keep-alive packets? > the service simply shutsdown on > client side after 5 mins. They have ~ 400 client concurrently. And I > am clueless! Just handle OnSessionClose properly and you should be safe, send-errors are handled by the component internally. > > Best Regards, > > Gorkem Ates > > > ----- Original Message ----- > From: "Arno Garrels" <[EMAIL PROTECTED]> > To: "ICS support mailing" <twsocket@elists.org> > Sent: Friday, March 09, 2007 4:08 PM > Subject: Re: [twsocket] Problem with web server socket > closingaftererroneoussend > > >> Fastream Technologies wrote: >>> Do I need to call shutdown on an errenous socket? >> >> Not needed. 10054 Connection reset by peer doesn't mean >> an error, the peer simply hung up the line. >> >>> I think you did not >>> read what I wrote carefully. I have connections objects hanging on a >>> modified MT HTTP server. >> >> As you wrote, OnClientClose will be called immediately, so cleanup >> can be done from there, or am I missing something? >> >> --- >> Arno Garrels [TeamICS] >> http://www.overbyte.be/eng/overbyte/teamics.html >> >> >> >>> >>> Regards, >>> >>> SZ >>> >>> ----- Original Message ----- >>> From: "Wilfried Mestdagh" <[EMAIL PROTECTED]> >>> To: "ICS support mailing" <twsocket@elists.org> >>> Sent: Friday, March 09, 2007 3:50 PM >>> Subject: Re: [twsocket] Problem with web server socket closing >>> aftererroneous send >>> >>> >>>> Hello Fastream, >>>> >>>> You should do nothing. It is the task of the client to reconnect if >>>> session is broken. >>>> >>>> --- >>>> Rgds, Wilfried [TeamICS] >>>> http://www.overbyte.be/eng/overbyte/teamics.html >>>> http://www.mestdagh.biz >>>> >>>> Friday, March 9, 2007, 11:10, Fastream Technologies wrote: >>>> >>>>> Hello, >>>> >>>>> I have the following scenario: >>>> >>>>> 1) Send() called >>>>> 2) 10054 returned >>>>> 3) Immediately by ICS OnClientClosed called >>>>> 4) I detect the error in socket >>>> >>>>> What should I do now? Should I call shutdown? Will the onclosed be >>>>> called again if I do so? Which event will it call if not? >>>>> Meanwhile, when errors occur, sockets stay hung! BTW, ICS web >>>>> server code does not handle socket errors!! >>>> >>>>> Regards, >>>> >>>>> SZ >>>> >>>> >>>> -- >>>> To unsubscribe or change your settings for TWSocket mailing list >>>> please goto http://www.elists.org/mailman/listinfo/twsocket >>>> Visit our website at http://www.overbyte.be >> -- >> To unsubscribe or change your settings for TWSocket mailing list >> please goto http://www.elists.org/mailman/listinfo/twsocket >> Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
