Re: [twsocket] Is this a bug or a missing feature in wsocket.pas?
Hi, I haven't read the full posting, but I recognise the error #. 10053 are common in the last week with a big client of ours.. What causes them (in our case) is poor connectivity including firewalls. The computer trying to connect can't make a connection, but it isn't reaching the destination. I can explain in detail the packet sequence that causes this but it would be boring. This error is practically the same as connection refused, but that a firewall in the middle is probably doing the refusal. Regards David Wilfried Mestdagh wrote: > Hello, > > >> So how to overcome it? Francois says the Winsock would timeout at some time >> and raise an error but that does not seem to be the case! Seems to me that >> > > The 10053 is in OnSessionClosed yes ? So all you have to do is reconnect > over there. > > >> there are CLOSE_WAIT state sockets aggregating and when they reach a certain >> amount, Accept() no longer works! >> > > You mean at server side ? Correct if there are too many sockets in use > (including the sockets in WAIT state) they use non pagable memory. When > all memory is used you cannot create a socket until memory becaumes > available again. So the server has to have the amount of memory needed > for his maximum predicted amount of clients and yes with some reserve > because connection can break. > > --- > Rgds, Wilfried [TeamICS] > http://www.overbyte.be/eng/overbyte/teamics.html > http://www.mestdagh.biz > > -- 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
Re: [twsocket] Is this a bug or a missing feature in wsocket.pas?
Hello, > So how to overcome it? Francois says the Winsock would timeout at some time > and raise an error but that does not seem to be the case! Seems to me that The 10053 is in OnSessionClosed yes ? So all you have to do is reconnect over there. > there are CLOSE_WAIT state sockets aggregating and when they reach a certain > amount, Accept() no longer works! You mean at server side ? Correct if there are too many sockets in use (including the sockets in WAIT state) they use non pagable memory. When all memory is used you cannot create a socket until memory becaumes available again. So the server has to have the amount of memory needed for his maximum predicted amount of clients and yes with some reserve because connection can break. --- Rgds, Wilfried [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html http://www.mestdagh.biz -- 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
Re: [twsocket] Is this a bug or a missing feature in wsocket.pas?
Hello Francois, I get the 10053 from the client side winsock whereas only my server is not working for the client so the problem must be there! Is it clear now? Regards, SZ - Original Message - From: "Francois Piette" <[EMAIL PROTECTED]> To: "ICS support mailing" Sent: Wednesday, July 25, 2007 4:20 PM Subject: Re: [twsocket] Is this a bug or a missing feature in wsocket.pas? >> So how to overcome it? Francois says the Winsock would timeout at some > time >> and raise an error but that does not seem to be the case! > > Well you are telling me you get the error 10053... > > -- > [EMAIL PROTECTED] > http://www.overbyte.be > > - Original Message - > From: "Fastream Technologies" <[EMAIL PROTECTED]> > To: "ICS support mailing" > Sent: Wednesday, July 25, 2007 2:39 PM > Subject: Re: [twsocket] Is this a bug or a missing feature in wsocket.pas? > > >> > Hello, >> > >> >> Why would a servef all into a state in which when a client connects it >> >> sees >> >> 10053? I see 10053 when I connect to my customer's site with HTTP > client >> >> demo after 2 hours! Not 10060, 10061 but 10053! >> > >> > A 10053 is 'software caused connection abort'. Normally this is a >> > routing or some other malfunction somewhere in between the 2 peer. >> > Winsock will generate this error in one of the case you describe in >> > your >> > first mail. >> >> So how to overcome it? Francois says the Winsock would timeout at some > time >> and raise an error but that does not seem to be the case! Seems to me >> that >> there are CLOSE_WAIT state sockets aggregating and when they reach a > certain >> amount, Accept() no longer works! >> >> Best 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
Re: [twsocket] Is this a bug or a missing feature in wsocket.pas?
> So how to overcome it? Francois says the Winsock would timeout at some time > and raise an error but that does not seem to be the case! Well you are telling me you get the error 10053... -- [EMAIL PROTECTED] http://www.overbyte.be - Original Message - From: "Fastream Technologies" <[EMAIL PROTECTED]> To: "ICS support mailing" Sent: Wednesday, July 25, 2007 2:39 PM Subject: Re: [twsocket] Is this a bug or a missing feature in wsocket.pas? > > Hello, > > > >> Why would a servef all into a state in which when a client connects it > >> sees > >> 10053? I see 10053 when I connect to my customer's site with HTTP client > >> demo after 2 hours! Not 10060, 10061 but 10053! > > > > A 10053 is 'software caused connection abort'. Normally this is a > > routing or some other malfunction somewhere in between the 2 peer. > > Winsock will generate this error in one of the case you describe in your > > first mail. > > So how to overcome it? Francois says the Winsock would timeout at some time > and raise an error but that does not seem to be the case! Seems to me that > there are CLOSE_WAIT state sockets aggregating and when they reach a certain > amount, Accept() no longer works! > > Best 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
Re: [twsocket] Is this a bug or a missing feature in wsocket.pas?
> Hello, > >> Why would a servef all into a state in which when a client connects it >> sees >> 10053? I see 10053 when I connect to my customer's site with HTTP client >> demo after 2 hours! Not 10060, 10061 but 10053! > > A 10053 is 'software caused connection abort'. Normally this is a > routing or some other malfunction somewhere in between the 2 peer. > Winsock will generate this error in one of the case you describe in your > first mail. So how to overcome it? Francois says the Winsock would timeout at some time and raise an error but that does not seem to be the case! Seems to me that there are CLOSE_WAIT state sockets aggregating and when they reach a certain amount, Accept() no longer works! Best 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
Re: [twsocket] Is this a bug or a missing feature in wsocket.pas?
Hello, > Why would a servef all into a state in which when a client connects it sees > 10053? I see 10053 when I connect to my customer's site with HTTP client > demo after 2 hours! Not 10060, 10061 but 10053! A 10053 is 'software caused connection abort'. Normally this is a routing or some other malfunction somewhere in between the 2 peer. Winsock will generate this error in one of the case you describe in your first mail. --- Rgds, Wilfried [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html http://www.mestdagh.biz -- 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
Re: [twsocket] Is this a bug or a missing feature in wsocket.pas?
Why would a servef all into a state in which when a client connects it sees 10053? I see 10053 when I connect to my customer's site with HTTP client demo after 2 hours! Not 10060, 10061 but 10053! Best Regards, SZ - Original Message - From: "Francois Piette" <[EMAIL PROTECTED]> To: "ICS support mailing" Sent: Wednesday, July 25, 2007 12:52 PM Subject: Re: [twsocket] Is this a bug or a missing feature in wsocket.pas? >> Ok then how do we move the sockets out of CLOSE_WAIT state when the > closing >> sequence is incomplete because of missing client packets?? Do not assume > we >> are using LAN and no-packet-loss networks. > > Winsock will timeout and give an error. > > -- > [EMAIL PROTECTED] > 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
Re: [twsocket] Is this a bug or a missing feature in wsocket.pas?
> Ok then how do we move the sockets out of CLOSE_WAIT state when the closing > sequence is incomplete because of missing client packets?? Do not assume we > are using LAN and no-packet-loss networks. Winsock will timeout and give an error. -- [EMAIL PROTECTED] 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
Re: [twsocket] Is this a bug or a missing feature in wsocket.pas?
Ok then how do we move the sockets out of CLOSE_WAIT state when the closing sequence is incomplete because of missing client packets?? Do not assume we are using LAN and no-packet-loss networks. Regards, SZ - Original Message - From: "Arno Garrels" <[EMAIL PROTECTED]> To: "ICS support mailing" Sent: Wednesday, July 25, 2007 9:50 AM Subject: Re: [twsocket] Is this a bug or a missing feature in wsocket.pas? >> Abort() IMHO. Is this correct? > > No, since receiving this notification from winsock does not > necessarily mean that all data has been received on the > application level. > > -- > Arno Garrels [TeamICS] > http://www.overbyte.be/eng/overbyte/teamics.html > > Fastream Technologies wrote: >> Hello, >> >> I mean the FD_CLOSE() is called when a close is detected right. >> However, the last two lines calling Close() should be changed with >> Abort() IMHO. Is this correct? >> >> Thanks, >> >> SZ >> >> - Original Message - >> From: "Fastream Technologies" <[EMAIL PROTECTED]> >> To: "ICS support mailing" >> Sent: Wednesday, July 25, 2007 12:03 AM >> Subject: Is this a bug or a missing feature in wsocket.pas? >> >> >>> Hello, >>> >>> In the description of winsock error 10053 which I get with my proxy, >>> I read: >>> >>> "TCP/IP scenario: A connection will timeout if the local system >>> doesn't receive an (ACK)nowledgement for data sent. It would also >>> timeout if a (FIN)ish TCP packet is not ACK'd (and even if the FIN >>> is ACK'd, it will eventually timeout if a FIN is not returned)." >>> >>> Is the case in the last sentence addressed by ICS? I mean, what to >>> do to sockets in CLOSE_WAIT state? I normally destruct my >>> thttpconnection instance (or send to pool) in a Postthreadmessage >>> posted in OnSessionClosed. Is there a better way to do it? >>> >>> Best 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
Re: [twsocket] Is this a bug or a missing feature in wsocket.pas?
> Abort() IMHO. Is this correct? No, since receiving this notification from winsock does not necessarily mean that all data has been received on the application level. -- Arno Garrels [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html Fastream Technologies wrote: > Hello, > > I mean the FD_CLOSE() is called when a close is detected right. > However, the last two lines calling Close() should be changed with > Abort() IMHO. Is this correct? > > Thanks, > > SZ > > - Original Message - > From: "Fastream Technologies" <[EMAIL PROTECTED]> > To: "ICS support mailing" > Sent: Wednesday, July 25, 2007 12:03 AM > Subject: Is this a bug or a missing feature in wsocket.pas? > > >> Hello, >> >> In the description of winsock error 10053 which I get with my proxy, >> I read: >> >> "TCP/IP scenario: A connection will timeout if the local system >> doesn't receive an (ACK)nowledgement for data sent. It would also >> timeout if a (FIN)ish TCP packet is not ACK'd (and even if the FIN >> is ACK'd, it will eventually timeout if a FIN is not returned)." >> >> Is the case in the last sentence addressed by ICS? I mean, what to >> do to sockets in CLOSE_WAIT state? I normally destruct my >> thttpconnection instance (or send to pool) in a Postthreadmessage >> posted in OnSessionClosed. Is there a better way to do it? >> >> Best 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
Re: [twsocket] Is this a bug or a missing feature in wsocket.pas?
Hello, I mean the FD_CLOSE() is called when a close is detected right. However, the last two lines calling Close() should be changed with Abort() IMHO. Is this correct? Thanks, SZ - Original Message - From: "Fastream Technologies" <[EMAIL PROTECTED]> To: "ICS support mailing" Sent: Wednesday, July 25, 2007 12:03 AM Subject: Is this a bug or a missing feature in wsocket.pas? > Hello, > > In the description of winsock error 10053 which I get with my proxy, I > read: > > "TCP/IP scenario: A connection will timeout if the local system doesn't > receive an (ACK)nowledgement for data sent. It would also timeout if a > (FIN)ish TCP packet is not ACK'd (and even if the FIN is ACK'd, it will > eventually timeout if a FIN is not returned)." > > Is the case in the last sentence addressed by ICS? I mean, what to do to > sockets in CLOSE_WAIT state? I normally destruct my thttpconnection > instance (or send to pool) in a Postthreadmessage posted in > OnSessionClosed. Is there a better way to do it? > > Best 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
[twsocket] Is this a bug or a missing feature in wsocket.pas?
Hello, In the description of winsock error 10053 which I get with my proxy, I read: "TCP/IP scenario: A connection will timeout if the local system doesn't receive an (ACK)nowledgement for data sent. It would also timeout if a (FIN)ish TCP packet is not ACK'd (and even if the FIN is ACK'd, it will eventually timeout if a FIN is not returned)." Is the case in the last sentence addressed by ICS? I mean, what to do to sockets in CLOSE_WAIT state? I normally destruct my thttpconnection instance (or send to pool) in a Postthreadmessage posted in OnSessionClosed. Is there a better way to do it? Best 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
