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 destinatio
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
ing"
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!
>
>
echnologies" <[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 connect
> 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
> routin
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
AIL 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
> 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 unsu
ED]>
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 da
> 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 t
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:
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 w
12 matches
Mail list logo
