Article View: borland.public.cppbuilder.internet.socket
Article #3601Re: Help with socket error 10053
From: mike
Date: Mon, 04 Jul 2005 19:46
Date: Mon, 04 Jul 2005 19:46
60 lines
3128 bytes
3128 bytes
Hans, Thanks for replying. >Then it is very difficult to debug indeed. Is the OS different there ? > Or has the server much less RAM ? You should really count > your serverthreads so you know at which amount problems begin. Yes this is hard to debug. The server is running 2000server and it does not have less ram then other sites where all work fine. I will make a change to the server software to count the threads that are open when the first 10053 error occurs and place that in a log file. At this point I am not sure what the count is. > Did you try to delete all threads, Close() the TServerSocket and then > to Open() it again ? No I have not tried that yet, but will modify the server software to do this at the first 10053 received to see if this clears it up. If I understand the error message description properly, the server is sending a TCP message and not getting back the ACK from the client. Is it possible that a router somewhere in the mix could be causing this to happen. If so do you have any insight as to what I could ask the site to look for on the router. I am not a router guy so I am at a bit of a loss on that. It may take me a few days to get the software modified and installed at the site to test. Boy this is troublesome. Thanks for the assitance. Mike "Hans Galema" <notused@notused.nl> wrote in message news:42c983b3$1@newsgroups.borland.com... > mike wrote: > >> I do have the same software running at other sites without any of the >> above problems. > > Then it is very difficult to debug indeed. Is the OS different there ? > Or has the server much less RAM ? You should really count > your serverthreads so you know at which amount problems begin. > >> But what I don't understand is why it could possibly be happening, and >> also, once it starts to happen what can I do with the host application to >> attempt to correct the situation. > > Did you try to delete all threads, Close() the TServerSocket and then > to Open() it again ? > > Please have a look at the way you reply. It makes no sence to reply > selective and also totallly. > > Hans.
Technical Details
Message-ID:
<42c99215@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!news.glorb.com!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mailReferences:
<42c57628$1@newsgroups.borland.com> <42c653f0@newsgroups.borland.com> <42c6a39e$1@newsgroups.borland.com> <42c983b3$1@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 11508e,456a07fc926312d1 X-Google-Attributes: gid11508e,public X-Google-Language: ENGLISH,ASCII-7-bit From: "mike" <mfbrowne@earthlink.nnet> Newsgroups: borland.public.cppbuilder.internet.socket References: <42c57628$1@newsgroups.borland.com> <42c653f0@newsgroups.borland.com> <42c6a39e$1@newsgroups.borland.com> <42c983b3$1@newsgroups.borland.com> Subject: Re: Help with socket error 10053 Date: Mon, 4 Jul 2005 15:46:30 -0400 Lines: 62 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2180 X-RFC2646: Format=Flowed; Response X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 NNTP-Posting-Host: 68.204.189.169 Message-ID: <42c99215@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1120506389 68.204.189.169 (4 Jul 2005 12:46:29 -0700) Path: arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!news.glorb.com!newsfeeds.ihug.co.nz!ihug.co.nz!newsgroups.borland.com!not-for-mail